CVE-2024-29059
.NET Framework Information Disclosure Vulnerability
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Error messages leak information. Some WAFs can scan responses and hide error pages and stack traces.
Also consider: custom error pages
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-29059 being exploited?
Yes. CVE-2024-29059 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-29059?
CVE-2024-29059 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-29059?
Yes. A fix has been recorded for CVE-2024-29059. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-29059 affect?
CVE-2024-29059 affects microsoft:.net_framework. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 2.0.0 and < 3.0.50727.8976
- affected>= 3.0.0 and < 3.0.50727.8976
- affected>= 3.5.0 and < 3.0.50727.8976
- affected>= 3.5.0 and < 3.0.30729.8959
- affected>= 10.0.0 and < 10.0.10240.20402
- affected>= 4.7.0 and < 4.7.04081.03
- affected>= 4.8.0 and < 4.8.04690.02
- affected>= 4.8.1 and < 4.8.09214.01
- affected>= 4.7.0 and < 4.7.04081.03
- affected>= 4.7.0 and < 4.7.04081.03
- affected>= 4.8.0 and < 4.8.04690.02
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept · 1 Nuclei template
- .NET Framework - Leaking ObjRefs via HTTP .NET Remoting · detection template · high
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 4 Feb 2025 (SSVC 2.0.3).
timeline
- 11 Mar 2024First proof-of-concept repository on GitHub (unvetted)
- 23 Mar 2024Published · 12 days later
- 4 Feb 2025Added to CISA KEV (exploited in the wild) · 318 days (about 11 months) later
- 4 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 25 Feb 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 239 days (about 8 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisorymsrc.microsoft.com /update-guide/vulnerability/CVE-2024-29059
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-29059
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.