dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 26 Aug 2024.
Windows 10 1507Operating system · Microsoft

CVE-2018-0824

HIGH · 8.8 CVSS v3.1 Published 2018-05-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A remote code execution vulnerability exists in Microsoft COM for Windows due to improper handling of serialized objects. An attacker could exploit this by sending specially crafted serialized data to a vulnerable system, potentially executing arbitrary code with the privileges of the targeted user.

MitigationApply the relevant Microsoft security update (KB4093118 for Windows 10/Server 2016, corresponding patches for other versions) to all affected Windows systems via Windows Update, WSUS, or manual patch deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:all versions
Windows 10 1607Operating system
Affected:all versions
Windows 10 1703Operating system
Affected:all versions
Windows 10 1709Operating system
Affected:all versions
Windows 10 1803Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version
    Run 'winver' or 'systeminfo' from command prompt to obtain the exact Windows version and build number
    Affected if The version is Windows 10 1507, 1607, 1703, 1709, 1803, Windows 7, Windows 8.1, or Windows Rt 8.1
  2. Verify security update status
    Open Windows Update history or run 'wmic qfe list' to list installed updates. Look for the Microsoft security update released for CVE-2018-0824
    Affected if The specific security update for CVE-2018-0824 is not listed among installed updates
  3. Confirm COM serialization is in use
    Check if applications or services that use COM serialization (such as .NET remoting, DCOM, or custom serialized COM objects) are running. Inspect running services and scheduled tasks for COM-based components
    Affected if COM serialization features are actively used and the system remains unpatched

A system is affected if it runs any of the listed Windows versions (Windows 7 through Windows 10 1803) AND the CVE-2018-0824 security update has not been applied, with COM serialization capabilities present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply the relevant Microsoft security update (KB4093118 for Windows 10/Server 2016, corresponding patches for other versions) to all affected Windows systems via Windows Update, WSUS, or manual patch deployment.

Recommended fix High confidence

For systems currently on Windows 10 1803 or earlier, upgrade to a supported Windows 10 release (1809 or later) or Windows 11; for Windows 7/8.1, upgrade to Windows 10/11 or Windows Server 2016/2019/2022

  1. Open Windows Update settings on the affected system
  2. Check for and install all pending Windows updates, particularly the security updates released in 2018
  3. If automatic updates are disabled, manually download and install the relevant security update from the Microsoft Update Catalog
  4. For Windows 7/8.1 systems, ensure Extended Security Updates (ESU) are enabled if the system is past end of support
  5. After installation, restart the system to complete the patch deployment
  6. Verify the update was successfully installed by checking the installed updates list
Caveat Windows 7 and Windows 8.1 are end-of-life; extended security updates require paid enrollment; upgrading from Windows 7 may require hardware compatibility checks and application remediation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0824 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0824 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data