CVE-2019-1405
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 · uneditedAn elevation of privilege vulnerability exists when the Windows Universal Plug and Play (UPnP) service improperly allows COM object creation, aka 'Windows UPnP Service Elevation of Privilege Vulnerability'.
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 · moderate confidenceThe Windows UPnP (Universal Plug and Play) service contains a flaw that improperly permits COM object creation, enabling a local attacker to elevate privileges from a standard user account to SYSTEM level access.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Windows version is affectedRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and check if the version matches Windows 10 1507, 1607, 1709, 1803, 1809, 1903, Windows 7, or Windows 8.1Affected if The installed Windows version is one of the listed affected versions and the security update is not installed
-
Check for security update installationOpen Control Panel > Programs > Programs and Features > View installed updates, or run 'wmic qfe list' to list installed hotfixes, and search for the security update addressing CVE-2019-1405Affected if The security update for CVE-2019-1405 is not installed on the system
-
Verify UPnP service statusRun 'services.msc' and locate the 'UPnP Device Host' service (upnphost), or run 'sc query upnphost' from command promptAffected if The UPnP Device Host service is running and the system lacks the security update
User is affected if running an affected Windows version (7, 8.1, or Windows 10 1507-1903) without the CVE-2019-1405 security update installed, and the UPnP service is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Microsoft security update for CVE-2019-1405, typically delivered via Windows Update or enterprise patch management systems.
- Install the November 2019 security update from Microsoft Update Catalog for your specific Windows version
- For Windows 10 1903: Install KB4524570 or later cumulative update
- For Windows 10 1809: Install KB4524570 or later cumulative update
- For Windows 10 1803: Install KB4524569 or later cumulative update
- For Windows 10 1709: Install KB4524568 or later cumulative update
- For Windows 10 1607: Install KB4524567 or later cumulative update
- For Windows 10 1507: Install KB4524566 or later cumulative update
- For Windows 8.1: Install KB4524565 (November 2019 Security Only Quality Update) or KB4524564 (November 2019 Monthly Quality Rollup)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1405 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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