Vulnerability record · CVE-2018-0824 · published 9 May 2018
CVE-2018-0824: Microsoft COM for Windows deserialization remote code execution
Microsoft · Windows 10 1507
Microsoft COM for Windows fails to properly handle serialized objects, allowing untrusted data deserialization (CWE-502). A crafted serialized object can trigger remote code execution on affected Windows versions, and the flaw is listed in CISA KEV, so it is a confirmed exploited target.
Description
A remote code execution vulnerability exists in "Microsoft COM for Windows" when it fails to properly handle serialized objects, aka "Microsoft COM for Windows Remote Code Execution Vulnerability." This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Automated analysis
critical priorityIt is in CISA KEV with confirmed exploitation, a public exploit, high EPSS and a CVSS of 8.8 allowing remote code execution.
What it is
Microsoft COM for Windows fails to properly handle serialized objects, allowing untrusted data deserialization (CWE-502). A crafted serialized object can trigger remote code execution on affected Windows versions, and the flaw is listed in CISA KEV, so it is a confirmed exploited target.
Impact
An attacker can execute arbitrary code in the context of the affected process or user, leading to full compromise of confidentiality, integrity and availability. CVSS 3.1 scores 8.8 (HIGH) with all three impact metrics rated High.
Attack surface
The vector is network-reachable (AV:N) with low complexity and no privileges required, but user interaction is required (UI:R), meaning a victim must open or handle a crafted serialized object. No authentication is needed on the attacker's side.
Exploitation
CVE-2018-0824 is in CISA KEV (added 2024-08-05) and has a public Exploit-DB entry, confirming real-world exploitation. EPSS 30-day probability is 0.73185 (99.4th percentile), indicating high likelihood of attempted exploitation.
What to do
- Apply the Microsoft security update referenced in the MSRC advisory for CVE-2018-0824 on all affected Windows versions.
- If patching cannot be completed immediately, follow CISA KEV required action: apply vendor mitigations or discontinue use of the affected product.
- Restrict handling of untrusted serialized COM objects and block known malicious file types at email and web gateways.
- Enforce least privilege and application allowlisting to limit the impact of code execution if a crafted object is opened.
- Monitor for and remove end-of-life systems such as Windows 7, Windows Server 2008 and Windows Server 2008 R2 that may lack full vendor support.
Detection
- Hunt for processes spawning from COM surrogate or Office applications that then execute scripting engines or unusual child processes.
- Monitor for known Exploit-DB 44906 indicators and related serialized object file names or extensions in email and web traffic.
- Alert on suspicious COM object instantiation events and unexpected CLSID access in endpoint telemetry.
- Correlate Windows event logs for unusual process creation, module loads and network connections from COM-related processes.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2018-0824 to the Known Exploited Vulnerabilities catalog on 5 August 2024 as "Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability". Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Federal deadline 26 August 2024.
Affected products
13 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/104030 | Broken LinkThird Party AdvisoryVDB Entry |
| http://www.securitytracker.com/id/1040848 | Broken LinkThird Party AdvisoryVDB Entry |
| https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0824 | PatchVendor Advisory |
| https://www.exploit-db.com/exploits/44906/ | ExploitThird Party AdvisoryVDB Entry |
| http://www.securityfocus.com/bid/104030 | Broken LinkThird Party AdvisoryVDB Entry |
| http://www.securitytracker.com/id/1040848 | Broken LinkThird Party AdvisoryVDB Entry |
| https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0824 | PatchVendor Advisory |
| https://www.exploit-db.com/exploits/44906/ | ExploitThird Party AdvisoryVDB Entry |
| https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-0824 | US Government Resource |
Track CVE-2018-0824 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2018-0824), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.