Threats / Microsoft / CVE-2024-29059
CVE-2024-29059
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
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.
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
552 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.98832 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, .NET Framework. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-209 Error Message Info Leak — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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