CVE-2018-0824
Published: August 5, 2024
Official Description
Microsoft COM for Windows contains a deserialization of untrusted data vulnerability that allows for privilege escalation and remote code execution via a specially crafted file or script.
CISA KEV Advisory
Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability
Microsoft COM for Windows contains a deserialization of untrusted data vulnerability that allows for privilege escalation and remote code execution via a specially crafted file or script.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Risk Analysis
This deserialization of untrusted data vulnerability in Microsoft COM for Windows allows for privilege escalation and remote code execution. It is a high-severity issue with a very high EPSS score of 0.91517, indicating a high likelihood of exploitation, and is confirmed to be actively exploited.
Active exploitation of this vulnerability has been observed in the wild. It can be exploited via a specially crafted file or script, and is likely remotely exploitable.
Users should apply the latest security updates for Microsoft Windows to mitigate this deserialization vulnerability.
Technical Analysis
CVE-2018-0824 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2018-0824 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2018-0824 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1