Threats / Microsoft / CVE-2024-29059
CVE-2024-29059
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft .NET Framework vulnerability
Microsoft .NET Framework information disclosure vulnerability exposes ObjRef URI, enabling remote code execution. Actively exploited in the wild.
Verdict
Today item — known-exploited.
An information disclosure flaw in .NET Framework leaks ObjRef URI data that attackers can leverage to achieve remote code execution. High exploitation activity observed. Patch immediately.
CISA KEV Yes · 2025-02-045EPSS 0.98624 (verify live)6Exploit Public PoC7CVSS 7.53CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
596 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-02-04).
Probability (EPSS)
EPSS 0.98624 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C) · Affected: Microsoft, .NET Framework. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-209 Error Message Info Leak — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 319 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a request to trigger ObjRef URI exposure from a vulnerable .NET Framework application.
Business
Attacker gains visibility into internal object references and serialization details.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I analyze the leaked ObjRef URI to understand the application's object model and communication protocol.
Business
Reconnaissance phase complete; attacker maps the application architecture.
3
Lateral reach — past segmentation narrative 3
Attacker
I construct a malicious payload using the exposed ObjRef information to invoke unintended code paths.
Business
Attacker achieves remote code execution on the affected system.
4
Data at risk — exfiltration narrative 4
Attacker
I execute arbitrary commands with the privileges of the .NET Framework process.
Business
System compromise, data theft, lateral movement, or persistent access established.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05