.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 PROB
- 99%
- EPSS %ILE
- 100%
- 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 91× in last 7d / 374× 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 1,323 total refreshes for this CVE.
- 2026-09-19 18:05 UTCVendor advisory
- 2026-09-19 18:05 UTCGHSA enrichment
- 2026-09-19 14:04 UTCVendor advisory
- 2026-09-19 14:04 UTCGHSA enrichment
- 2026-09-19 10:03 UTCVendor advisory
- 2026-09-19 10:03 UTCGHSA enrichment
- 2026-09-19 06:02 UTCVendor advisory
- 2026-09-19 06:02 UTCGHSA enrichment
- 2026-09-19 02:01 UTCVendor advisory
- 2026-09-19 02:01 UTCGHSA enrichment
- 2026-09-18 22:00 UTCVendor advisory
- 2026-09-18 22:00 UTCGHSA enrichment
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 17:59 UTCVendor advisory
- 2026-09-18 17:59 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 13:58 UTCVendor advisory
- 2026-09-18 13:58 UTCGHSA enrichment
- 2026-09-18 09:57 UTCVendor advisory
- 2026-09-18 09:57 UTCGHSA enrichment
- 2026-09-18 05:56 UTCVendor advisory
- 2026-09-18 05:55 UTCGHSA enrichment
- 2026-09-18 01:55 UTCVendor advisory
- 2026-09-18 01:55 UTCGHSA enrichment
- 2026-09-17 21:54 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-17 21:54 UTCGHSA enrichment
- 2026-09-17 17:53 UTCVendor advisory
- 2026-09-17 17:53 UTCGHSA enrichment
- 2026-09-17 13:51 UTCVendor advisory
- 2026-09-17 13:51 UTCGHSA enrichment
- 2026-09-17 09:50 UTCVendor advisory
- 2026-09-17 09:50 UTCGHSA enrichment
- 2026-09-17 05:49 UTCVendor advisory
- 2026-09-17 05:48 UTCGHSA enrichment
- 2026-09-17 01:45 UTCVendor advisory
- 2026-09-17 01:45 UTCGHSA enrichment
- 2026-09-16 21:44 UTCVendor advisory
- 2026-09-16 21:44 UTCGHSA enrichment
- 2026-09-16 17:43 UTCEG score recompute
- 2026-09-16 17:43 UTCVendor advisory
- 2026-09-16 17:43 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 13:42 UTCVendor advisory
- 2026-09-16 13:41 UTCGHSA enrichment
- 2026-09-16 09:39 UTCVendor advisory
- 2026-09-16 09:38 UTCGHSA enrichment
- 2026-09-16 05:37 UTCVendor advisory
- 2026-09-16 05:37 UTCGHSA enrichment
- 2026-09-16 01:37 UTCVendor advisory
- 2026-09-16 01:37 UTCGHSA enrichment
- 2026-09-15 21:36 UTCVendor advisory
- 2026-09-15 21:36 UTCGHSA enrichment
- 2026-09-15 17:33 UTCVendor advisory
- 2026-09-15 17:33 UTCGHSA enrichment
- 2026-09-15 13:32 UTCVendor advisory
- 2026-09-15 13:32 UTCGHSA enrichment
- 2026-09-15 09:31 UTCVendor advisory
- 2026-09-15 09:31 UTCGHSA enrichment
- 2026-09-15 05:30 UTCVendor advisory
- 2026-09-15 05:30 UTCGHSA enrichment
- 2026-09-15 01:28 UTCVendor advisory
- 2026-09-15 01:28 UTCGHSA enrichment
- 2026-09-14 21:27 UTCVendor advisory
- 2026-09-14 21:27 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 17:26 UTCVendor advisory
- 2026-09-14 17:26 UTCGHSA enrichment
- 2026-09-14 13:25 UTCVendor advisory
- 2026-09-14 13:25 UTCGHSA enrichment
- 2026-09-14 09:24 UTCVendor advisory
- 2026-09-14 09:24 UTCGHSA enrichment
- 2026-09-14 05:23 UTCVendor advisory
- 2026-09-14 05:23 UTCGHSA enrichment
- 2026-09-14 01:22 UTCVendor advisory
- 2026-09-14 01:22 UTCGHSA enrichment
- 2026-09-13 21:21 UTCVendor advisory
- 2026-09-13 21:21 UTCGHSA enrichment
- 2026-09-13 17:20 UTCVendor advisory
- 2026-09-13 17:20 UTCGHSA enrichment
- 2026-09-13 13:19 UTCVendor advisory
- 2026-09-13 13:19 UTCGHSA enrichment
- 2026-09-13 09:18 UTCVendor advisory
- 2026-09-13 09:17 UTCGHSA enrichment
- 2026-09-13 05:17 UTCVendor advisory
- 2026-09-13 05:17 UTCGHSA enrichment
- 2026-09-13 01:16 UTCVendor advisory
- 2026-09-13 01:16 UTCGHSA enrichment
- 2026-09-12 21:15 UTCVendor advisory
- 2026-09-12 21:15 UTCGHSA enrichment
- 2026-09-12 17:14 UTCVendor advisory
- 2026-09-12 17:14 UTCGHSA enrichment
- 2026-09-12 13:13 UTCVendor advisory
- 2026-09-12 13:13 UTCGHSA enrichment
- 2026-09-12 09:12 UTCVendor advisory
- 2026-09-12 09:12 UTCGHSA enrichment
- 2026-09-12 05:11 UTCVendor advisory
- 2026-09-12 05:11 UTCGHSA enrichment
- 2026-09-12 01:10 UTCVendor advisory
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
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.