Skip to content
Server Security Center
KEVhigh7.5

CVE-2024-29059: Microsoft .NET Framework Information Disclosure

Microsoft .NET Framework · listed in the CISA catalog of actively exploited vulnerabilities since 2025-02-04.

CVSS v3.1 (CVE record)
7.5
high
EPSS (exploit probability, 30 days)
99%
among the highest 0.1% of all CVEs
Added to CISA KEV
2025-02-04
US federal due date 2025-02-25
Automatable (CISA SSVC)
yes
technical impact: partial

CVE-2024-29059 explained

CVE-2024-29059 is an information disclosure vulnerability in Microsoft .NET Framework on Windows. It exposes the ObjRef URI to an attacker, which can ultimately enable remote code execution. CISA lists it as known to be exploited, so affected systems should be patched promptly.

Impact

A remote, unauthenticated attacker can exploit this over the network with low complexity and no user interaction. The direct effect is high confidentiality impact through exposure of the ObjRef URI in error output. According to the description, this disclosure can ultimately enable remote code execution. CISA rates it automatable, meaning it can be exploited at scale, with partial technical impact. Attackers are known to use it.

Who is affected

Many .NET Framework versions on Windows client and server releases are affected. Fixed builds: .NET Framework 4.8 and 3.5 AND 4.8 at 4.8.04690.02; 4.6.2 through 4.7.2 combinations at 4.7.04081.03; 3.5 AND 4.8.1 at 4.8.09214.01; 3.5 AND 4.6/4.6.2 on Windows 10 at 10.0.10240.20402; 2.0 SP2, 3.0 SP2 and 3.5 at 3.0.50727.8976; 3.5.1 on Windows Server 2008 R2 SP1 at 3.0.30729.8959. Earlier builds are affected.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft .NET Framework contains an information disclosure vulnerability that exposes the ObjRef URI to an attacker, ultimately enabling remote code execution.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft .NET Framework 4.8Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016, Windows Server 2016 (Server Core installation), Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)
    Affected
    • < 4.8.04690.02
    Fixed in
    • 4.8.04690.02
  • Microsoft .NET Framework 3.5 AND 4.8Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows Server 2022 (Server Core installation), Windows 11 version 21H2 for x64-based Systems, Windows 11 version 21H2 for ARM64-based Systems, Windows 10 Version 21H2 for 32-bit Systems, Windows 10 Version 21H2 for ARM64-based Systems, Windows 10 Version 21H2 for x64-based Systems, Windows 10 Version 22H2 for x64-based Systems, Windows 10 Version 22H2 for ARM64-based Systems, Windows 10 Version 22H2 for 32-bit Systems
    Affected
    • < 4.8.04690.02
    Fixed in
    • 4.8.04690.02
  • Microsoft .NET Framework 3.5 AND 4.7.2Windows 10 Version 1809 for x64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016, Windows Server 2016 (Server Core installation)
    Affected
    • < 4.7.04081.03
    Fixed in
    • 4.7.04081.03
  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation), Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)
    Affected
    • < 4.7.04081.03
    Fixed in
    • 4.7.04081.03
  • Microsoft .NET Framework 3.5 AND 4.8.1Windows Server 2022, Windows Server 2022 (Server Core installation), Windows 11 version 21H2 for x64-based Systems, Windows 11 version 21H2 for ARM64-based Systems, Windows 10 Version 21H2 for 32-bit Systems, Windows 10 Version 21H2 for ARM64-based Systems, Windows 10 Version 21H2 for x64-based Systems, Windows 11 Version 22H2 for ARM64-based Systems, Windows 11 Version 22H2 for x64-based Systems, Windows 10 Version 22H2 for x64-based Systems, Windows 10 Version 22H2 for ARM64-based Systems, Windows 10 Version 22H2 for 32-bit Systems, Windows 11 Version 23H2 for ARM64-based Systems, Windows 11 Version 23H2 for x64-based Systems, Windows Server 2022, 23H2 Edition (Server Core installation)
    Affected
    • < 4.8.09214.01
    Fixed in
    • 4.8.09214.01
  • Microsoft .NET Framework 4.6.2Windows Server 2008 for 32-bit Systems Service Pack 2, Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation), Windows Server 2008 for x64-based Systems Service Pack 2, Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
    Affected
    • < 4.7.04081.03
    Fixed in
    • 4.7.04081.03
  • Microsoft .NET Framework 3.5 AND 4.6/4.6.2Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems
    Affected
    • < 10.0.10240.20402
    Fixed in
    • 10.0.10240.20402
  • Microsoft .NET Framework 2.0 Service Pack 2Windows Server 2008 for 32-bit Systems Service Pack 2, Windows Server 2008 for x64-based Systems Service Pack 2
    Affected
    • < 3.0.50727.8976
    Fixed in
    • 3.0.50727.8976
  • Microsoft .NET Framework 3.0 Service Pack 2Windows Server 2008 for 32-bit Systems Service Pack 2, Windows Server 2008 for x64-based Systems Service Pack 2
    Affected
    • < 3.0.50727.8976
    Fixed in
    • 3.0.50727.8976
  • Microsoft .NET Framework 3.5Windows Server 2012, Windows Server 2012 (Server Core installation), Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation)
    Affected
    • < 3.0.50727.8976
    Fixed in
    • 3.0.50727.8976
  • Microsoft .NET Framework 3.5.1Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
    Affected
    • < 3.0.30729.8959
    Fixed in
    • 3.0.30729.8959

How to fix it

  • Update to the fixed version for your product:
    • Microsoft .NET Framework 4.8: 4.8.04690.02
    • Microsoft .NET Framework 3.5 AND 4.8: 4.8.04690.02
    • Microsoft .NET Framework 3.5 AND 4.7.2: 4.7.04081.03
    • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2: 4.7.04081.03
    • Microsoft .NET Framework 3.5 AND 4.8.1: 4.8.09214.01
    • Microsoft .NET Framework 4.6.2: 4.7.04081.03
    Fixed versions for 5 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-29059
  • CISA's deadline for US federal agencies: 2025-02-25 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify every Windows system and the .NET Framework versions installed on it.
  2. Install the Microsoft security update that brings each .NET Framework install to the fixed build listed for its platform.
  3. Prioritize internet-facing servers and applications that use .NET Framework, given known exploitation.
  4. Follow the vendor advisory and CISA's required action; discontinue use where mitigations are unavailable.
  5. Restrict network exposure of .NET-based services to trusted networks where possible.
  6. Check exposed systems for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Partial – limited control or information

Weakness: CWE-209 Generation of Error Message Containing Sensitive Information

Questions about CVE-2024-29059

Is CVE-2024-29059 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-02-04, with a US federal due date of 2025-02-25. Whether it is used in ransomware campaigns is unknown.
Why does an information disclosure flaw matter so much?
The exposed ObjRef URI can ultimately enable remote code execution, according to the description. It requires no authentication or user interaction and CISA rates it automatable.
Which build do I need?
It depends on the .NET Framework version and Windows platform. For example, .NET Framework 4.8 needs 4.8.04690.02 and 4.8.1 needs 4.8.09214.01. Check the affected products list and vendor advisory for your platform.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.