CVE-2024-29059
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited.NET Framework Information Disclosure Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · low confidenceCVE-2024-29059 is a HIGH-severity information disclosure vulnerability affecting .NET Framework. The vulnerability allows an attacker to potentially access sensitive information through unspecified means within the .NET Framework runtime environment. Further technical details regarding the attack vector or specific vulnerable code paths are not available in the provided description.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.5= 4.7.2= 4.8= 3.5.1= 2.0= 3.0= 4.6= 4.6.2= 4.8.1= 4.7= 4.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed .NET Framework versionsOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full (for .NET 4.x) and HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3\ (for .NET 3.x/2.x). Check the Version value in each subkey to see which versions are installed.Affected if Any of the following versions are installed: 3.5, 3.5.1, 3.0, 2.0, 4.6, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, or 4.8.1
-
Check .NET Framework version via PowerShellRun Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' | Select-Object Version, Release in PowerShell. Also check Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3\Setup' for earlier versions.Affected if The Version or Release value matches any of the affected versions listed in the CVE (3.5, 3.5.1, 3.0, 2.0, 4.6, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, 4.8.1)
-
List installed features via Windows FeaturesOpen Control Panel > Programs and Features > Turn Windows features on or off. Look for .NET Framework entries to see which versions are enabled on the system.Affected if Any .NET Framework version matching the affected list is present in the Windows features list
A system is affected if it has any of the following .NET Framework versions installed and running: 3.5, 3.5.1, 3.0, 2.0, 4.6, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, or 4.8.1
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant Microsoft security patch for .NET Framework when released, and ensure systems are updated to the latest supported .NET Framework versions. Review Microsoft Security Response Center advisories for complete remediation steps.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data