.NET Framework Information Disclosure Vulnerability
CVE-2024-29059
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-02-04), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 9.0(high)
- EG Risk
- 96(Attend)EG Risk 96/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
March 23, 2024
Last Modified
October 28, 2025
Advisory Details (2)
Auto-updated Jun 5, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-29059Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-29059Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 63× in last 7d / 344× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 648 total refreshes for this CVE.
- 2026-07-23 02:35 UTCEG score recompute
- 2026-07-22 21:38 UTCEG score recompute
- 2026-07-22 21:38 UTCVendor advisory
- 2026-07-22 21:38 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 17:31 UTCGHSA enrichment
- 2026-07-22 13:29 UTCVendor advisory
- 2026-07-22 13:29 UTCGHSA enrichment
- 2026-07-22 09:28 UTCVendor advisory
- 2026-07-22 09:28 UTCGHSA enrichment
- 2026-07-22 05:27 UTCVendor advisory
- 2026-07-22 05:26 UTCGHSA enrichment
- 2026-07-22 01:25 UTCVendor advisory
- 2026-07-22 01:25 UTCGHSA enrichment
- 2026-07-21 21:24 UTCVendor advisory
- 2026-07-21 21:23 UTCGHSA enrichment
- 2026-07-21 17:22 UTCVendor advisory
- 2026-07-21 17:22 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:21 UTCVendor advisory
- 2026-07-21 13:21 UTCGHSA enrichment
- 2026-07-21 09:20 UTCVendor advisory
- 2026-07-21 09:20 UTCGHSA enrichment
- 2026-07-21 05:19 UTCVendor advisory
- 2026-07-21 05:18 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 01:17 UTCVendor advisory
- 2026-07-21 01:17 UTCGHSA enrichment
- 2026-07-20 21:16 UTCVendor advisory
- 2026-07-20 21:16 UTCGHSA enrichment
- 2026-07-20 17:15 UTCVendor advisory
- 2026-07-20 17:14 UTCGHSA enrichment
- 2026-07-20 13:12 UTCVendor advisory
- 2026-07-20 13:12 UTCGHSA enrichment
- 2026-07-20 09:12 UTCVendor advisory
- 2026-07-20 09:12 UTCGHSA enrichment
- 2026-07-20 05:11 UTCVendor advisory
- 2026-07-20 05:11 UTCGHSA enrichment
- 2026-07-20 01:10 UTCVendor advisory
- 2026-07-19 21:09 UTCVendor advisory
- 2026-07-19 21:09 UTCGHSA enrichment
- 2026-07-19 17:08 UTCVendor advisory
- 2026-07-19 17:08 UTCGHSA enrichment
- 2026-07-19 13:07 UTCVendor advisory
- 2026-07-19 13:07 UTCGHSA enrichment
- 2026-07-19 09:06 UTCVendor advisory
- 2026-07-19 09:06 UTCGHSA enrichment
- 2026-07-19 05:05 UTCVendor advisory
- 2026-07-19 05:05 UTCGHSA enrichment
- 2026-07-19 01:03 UTCGHSA enrichment
- 2026-07-18 21:01 UTCVendor advisory
- 2026-07-18 21:01 UTCGHSA enrichment
- 2026-07-18 16:59 UTCVendor advisory
- 2026-07-18 16:59 UTCGHSA enrichment
- 2026-07-18 12:57 UTCVendor advisory
- 2026-07-18 12:57 UTCGHSA enrichment
- 2026-07-18 08:56 UTCVendor advisory
- 2026-07-18 08:56 UTCGHSA enrichment
- 2026-07-18 04:55 UTCVendor advisory
- 2026-07-18 04:54 UTCGHSA enrichment
- 2026-07-18 00:53 UTCVendor advisory
- 2026-07-18 00:53 UTCGHSA enrichment
- 2026-07-17 20:52 UTCVendor advisory
- 2026-07-17 20:52 UTCGHSA enrichment
- 2026-07-17 16:51 UTCVendor advisory
- 2026-07-17 16:51 UTCGHSA enrichment
- 2026-07-17 12:48 UTCVendor advisory
- 2026-07-17 12:48 UTCGHSA enrichment
- 2026-07-17 08:47 UTCEG score recompute
- 2026-07-17 08:47 UTCVendor advisory
- 2026-07-17 08:47 UTCGHSA enrichment
- 2026-07-17 04:46 UTCVendor advisory
- 2026-07-17 04:46 UTCGHSA enrichment
- 2026-07-17 00:45 UTCVendor advisory
- 2026-07-17 00:45 UTCGHSA enrichment
- 2026-07-16 20:45 UTCVendor advisory
- 2026-07-16 20:45 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-16 16:43 UTCGHSA enrichment
- 2026-07-16 12:39 UTCGHSA enrichment
- 2026-07-16 08:39 UTCVendor advisory
- 2026-07-16 08:39 UTCGHSA enrichment
- 2026-07-16 04:38 UTCVendor advisory
- 2026-07-16 04:38 UTCGHSA enrichment
- 2026-07-16 00:37 UTCVendor advisory
- 2026-07-16 00:37 UTCGHSA enrichment
- 2026-07-15 20:36 UTCVendor advisory
- 2026-07-15 20:36 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 16:35 UTCVendor advisory
- 2026-07-15 16:35 UTCGHSA enrichment
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 12:34 UTCVendor advisory
- 2026-07-15 12:34 UTCGHSA enrichment
- 2026-07-15 08:33 UTCVendor advisory
- 2026-07-15 08:33 UTCGHSA enrichment
- 2026-07-15 04:31 UTCVendor advisory
- 2026-07-15 04:31 UTCGHSA enrichment
- 2026-07-15 00:29 UTCVendor advisory
- 2026-07-15 00:29 UTCGHSA enrichment
Publicly available exploits
(2 references)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCcodewhitesec/HttpRemotingObjRefLeakFirst seen Mar 11, 2024
Additional resources for leaking and exploiting ObjRefs via HTTP .NET Remoting (CVE-2024-29059)
Open source ↗ - Nucleihttp/cves/2024/CVE-2024-29059.yamlFirst seen Jan 1, 2024
.NET Framework - Leaking ObjRefs via HTTP .NET Remoting
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-209
Frequently asked(6)
What is CVE-2024-29059?
When was CVE-2024-29059 disclosed?
Is CVE-2024-29059 actively exploited?
What is the CVSS score of CVE-2024-29059?
Which products are affected by CVE-2024-29059?
How do I remediate CVE-2024-29059?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-29059
Is Your Infrastructure Affected by CVE-2024-29059?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.