basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2018-0824
CVE-2018-0824 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Windows vulnerability

Microsoft COM deserialization vulnerability in Windows allows remote code execution and privilege escalation through specially crafted files or scripts.

Verdict

Today item — known-exploited.

CVE-2018-0824 is a critical deserialization flaw enabling unauthenticated remote code execution with privilege escalation potential. High EPSS score and active exploitation in the wild indicate immediate threat to unpatched Windows systems.

CISA KEV Yes · 2024-08-053EPSS 0.73469 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
4 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 2024-08-05).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.73469 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious file or script that exploits unsafe deserialization in Windows COM to execute arbitrary code.
Business
Attacker gains code execution on victim systems, enabling data theft, malware deployment, or lateral movement within enterprise networks.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I leverage the code execution to escalate privileges from user context to system or administrator level.
Business
Elevated privileges allow complete system compromise, persistence mechanisms, and access to sensitive administrative functions and data.
3

Lateral reach — past segmentation narrative 3

Attacker
I distribute the malicious file through email, file sharing, or compromised websites to maximize infection surface.
Business
Widespread deployment across organizations results in mass system compromise, operational disruption, and potential regulatory compliance violations.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.