How to Fix CVE-2018-0824: Remote Code Execution in Windows

By Sai Kiran Pandrala

Patch immediately. CISA added CVE-2018-0824 to the Known Exploited Vulnerabilities catalog on 2024-08-05. Federal civilian agencies must remediate by 2024-08-26. Treat every internet-reachable instance as a priority patch.

What is CVE-2018-0824?

CVE-2018-0824 is a Remote Code Execution flaw in Microsoft Windows. It carries a CVSS base score of 7.5 (high). CISA confirmed real-world exploitation by adding it to the Known Exploited Vulnerabilities catalog on 2024-08-05.

From the source record: 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.

Why it matters in practice: KEV-listed CVEs draw continuous internet-wide scanning. Any unpatched, internet-reachable installation is on borrowed time. The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Windows matches a version listed in the Affected row above.

On Windows, check the installed version with PowerShell:

# Generic - list installed product versions
Get-CimInstance Win32_Product | Where-Object Name -like "*Windows*" | Select-Object Name, Version
# Windows updates installed (KB lookup)
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20

How to fix CVE-2018-0824

Apply the vendor patch. Target the patched build listed on the vendor advisory. The runnable command set below covers the most common deployment patterns for Windows.

Windows (PowerShell, run as administrator)

# 1) Backup affected service config
$stamp = Get-Date -Format yyyyMMdd-HHmm
$backup = "C:\Backup\windows-$stamp"
New-Item -ItemType Directory -Path $backup -Force | Out-Null

# 2) Install the latest Windows security updates (the patch for CVE-2018-0824 ships here)
Install-Module PSWindowsUpdate -Force -Scope CurrentUser -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Get-WindowsUpdate -MicrosoftUpdate -AcceptAll -Install -AutoReboot

# 3) Confirm the patch landed
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

Vendor-managed app on Windows (winget)

# Vendor advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0824
winget upgrade --all --silent --accept-package-agreements --accept-source-agreements
# or target the specific package:
winget search "Windows"
winget upgrade --id <PackageId> --silent

Complete PowerShell patch script

# Patch Windows for CVE-2018-0824
$log = "C:\Backup\CVE-2018-0824-patch.log"
"[{0}] Starting patch run" -f (Get-Date) | Tee-Object -FilePath $log -Append
try {
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\windows-$stamp"
    New-Item -ItemType Directory -Path $backup -Force | Out-Null
    # Backup hook - tailor for the product
    # Copy-Item "C:\Program Files\Windows" $backup -Recurse -ErrorAction SilentlyContinue

    if (-not (Get-Module -ListAvailable PSWindowsUpdate)) {
        Install-Module PSWindowsUpdate -Force -Scope CurrentUser
    }
    Import-Module PSWindowsUpdate
    Get-WindowsUpdate -MicrosoftUpdate -AcceptAll -Install -AutoReboot:$false -IgnoreReboot
    "[{0}] Updates installed" -f (Get-Date) | Tee-Object -FilePath $log -Append
    # Verify
    Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 | Out-File $log -Append
    "[{0}] Patch run complete - reboot at next maintenance window" -f (Get-Date) | Tee-Object -FilePath $log -Append
} catch {
    "[{0}] ERROR: $_" -f (Get-Date) | Tee-Object -FilePath $log -Append
    exit 1
}

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict the affected service via Windows Firewall

# Replace -RemoteAddress with your trusted admin range
New-NetFirewallRule -DisplayName "Block CVE-2018-0824 inbound" -Direction Inbound -Action Block -Protocol TCP -LocalPort 445,3389,5985
New-NetFirewallRule -DisplayName "Allow CVE-2018-0824 admin range" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 445,3389,5985 -RemoteAddress 10.10.10.0/24

Disable the vulnerable feature if the vendor advisory allows it

# Vendor advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0824
# Example: stopping a non-essential Windows service
Stop-Service -Name <ServiceName> -Force
Set-Service -Name <ServiceName> -StartupType Disabled

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

# Confirm KB / hotfix is present
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
# Confirm product version
Get-CimInstance Win32_Product | Where-Object Name -like "*Windows*" | Select-Object Name, Version

Expected: the patched build named in Fixed in (See vendor advisory) appears in the version column.

Also worth doing: pull recent log windows for any indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2018-8298: Access of resource using incompatible type in ChakraCore — Access of resource using incompatible type in ChakraCore
• How to Fix CVE-2018-8174: Out-of-bounds write in Microsoft Windows — Out-of-bounds write in Microsoft Windows
• How to Fix CVE-2018-8589: Elevation of Privilege in Microsoft Win32k , Elevation of Privilege in Microsoft Win32k
• How to Fix CVE-2018-8653: Remote Code Execution in Internet Explorer 9 , Remote Code Execution in Internet Explorer 9
• How to Fix CVE-2018-8405: Improper Resource Shutdown or Release in Microsoft DirectX Graphics Kernel (DXGKRNL) , Improper Resource Shutdown or Release in Microsoft DirectX Graphics Kernel (DXGKRNL)

Is CVE-2018-0824 being exploited in the wild?

Yes. CISA added CVE-2018-0824 to the Known Exploited Vulnerabilities catalog on 2024-08-05. KEV listing means at least one confirmed real-world exploitation report exists.

Do I have to take downtime to patch?

For most Microsoft Windows deployments, the patched build needs a service restart or device reboot. HA pairs and clusters can roll the upgrade by patching the standby first, failing over, then patching the former primary.

Will a WAF or IDS rule alone close CVE-2018-0824?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

How quickly should I act on CVE-2018-0824?

Within the standard patch cycle if the asset is internal-only. Inside one to two weeks for any internet-facing instance, sooner if compensating controls are not in place.

References

• Official vendor advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0824
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2018-0824
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• CISA KEV entry: "Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability" - added 2024-08-05, due 2024-08-26
• Additional reference: http://www.securityfocus.com/bid/104030
• Additional reference: http://www.securitytracker.com/id/1040848
• Additional reference: https://www.exploit-db.com/exploits/44906/

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*