CVE-2018-0824
Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability
Microsoft Windows
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 5 August 2024. US federal agencies were required to remediate it by 26 August 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 73%, which is higher than 99.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2018-0824 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2018-0824.
What does CVE-2018-0824 affect?
CVE-2018-0824 affects Microsoft Windows. 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.
How severe is CVE-2018-0824?
CVE-2018-0824 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 73%, higher than 99.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 26 August 2024.
How should organisations respond to CVE-2018-0824?
Apply the vendor patch for Microsoft Windows as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.