Microsoft .NET Framework Information Disclosure
CVE-2024-29059 is a high-severity generation of error message containing sensitive information vulnerability in Microsoft .NET Framework 4.8 from Microsoft, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.8.04690.02 as the first without the flaw, so updating Microsoft .NET Framework 4.8 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on February 4, 2025, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Microsoft .NET Framework 4.8 to 4.8.04690.02 or a later version.
- Update Microsoft .NET Framework 3.5 AND 4.8 to 4.8.04690.02 or a later version.
- Update Microsoft .NET Framework 3.5 AND 4.7.2 to 4.7.04081.03 or a later version.
- CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Microsoft .NET Framework 4.8 | 4.8.0 up to, but not including, 4.8.04690.02 | 4.8.04690.02 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.8 | 4.8.0 up to, but not including, 4.8.04690.02 | 4.8.04690.02 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.7.2 | 4.7.0 up to, but not including, 4.7.04081.03 | 4.7.04081.03 |
| Microsoft | Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 | 4.7.0 up to, but not including, 4.7.04081.03 | 4.7.04081.03 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.8.1 | 4.8.1 up to, but not including, 4.8.09214.01 | 4.8.09214.01 |
| Microsoft | Microsoft .NET Framework 4.6.2 | 4.7.0 up to, but not including, 4.7.04081.03 | 4.7.04081.03 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.6/4.6.2 | 10.0.0 up to, but not including, 10.0.10240.20402 | 10.0.10240.20402 |
| Microsoft | Microsoft .NET Framework 2.0 Service Pack 2 | 2.0.0 up to, but not including, 3.0.50727.8976 | 3.0.50727.8976 |
| Microsoft | Microsoft .NET Framework 3.0 Service Pack 2 | 3.0.0 up to, but not including, 3.0.50727.8976 | 3.0.50727.8976 |
| Microsoft | Microsoft .NET Framework 3.5 | 3.5.0 up to, but not including, 3.0.50727.8976 | 3.0.50727.8976 |
| Microsoft | Microsoft .NET Framework 3.5.1 | 3.5.0 up to, but not including, 3.0.30729.8959 | 3.0.30729.8959 |
| Microsoft | .net Framework | 3.5; 4.7.2; 4.8; 3.5.1; 2.0; 3.0; 4.6; 4.6.2; and 3 more ranges | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CNA (microsoft.com).
Official description
.NET Framework Information Disclosure Vulnerability
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Generation of Error Message Containing Sensitive Information
The product generates an error message that includes sensitive information about its environment, users, or associated data.
How developers prevent this class of flaw
- Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
- Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
- Debugging information should not make its way into a production release.
More Generation of Error Message Containing Sensitive Information vulnerabilities (CWE-209)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: active, automatable: yes, technical impact: partial).
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-29059US Government Resource
Other vulnerabilities in Microsoft .NET Framework 4.8
- 8.8 High severity
- 7.5 High severity
Recent Generation of Error Message Containing Sensitive Information vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.