CVE-2019-1405
Exploited in the wild. In CISA KEV since 2022‑03‑15. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
- Microsoft WindowsAffected: 7 for 32-bit Systems Service Pack 1Upgrade to: not statedAffected: 7 for x64-based Systems Service Pack 1Upgrade to: not statedAffected: 8.1 for 32-bit systemsUpgrade to: not statedAffected: 8.1 for x64-based systemsUpgrade to: not stated + 14 more branchesStated by: CVE record
- Microsoft Windows ServerAffected: 2008 R2 for x64-based Systems Service Pack 1 (Core installation)Upgrade to: not statedAffected: 2008 R2 for Itanium-Based Systems Service Pack 1Upgrade to: not statedAffected: 2008 R2 for x64-based Systems Service Pack 1Upgrade to: not statedAffected: 2008 for 32-bit Systems Service Pack 2 (Core installation)Upgrade to: not stated + 14 more branchesStated by: CVE record
- Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected: unspecifiedUpgrade to: not statedStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check whether you run one of these affected systems: Windows 7, Windows 8.1, Windows 10, Windows RT 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server (as listed).
- On each affected machine, confirm UPnP (Windows UPnP service) is installed/enabled in your environment.
- Apply the vendor update(s) for CVE-2019-1405 using Microsoft’s remediation guidance for this CVE.
- If you cannot patch immediately, temporarily disable or restrict the UPnP service based on Microsoft’s CVE guidance until updates can be applied.
- Verify after patching that the machine is updated per the Microsoft guidance and that the vulnerability is no longer present (via your patch compliance checks).
Coverage timeline
0 publishersAdded to CISA KEV catalog
Sourced from public security reporting — each date is when it was published, not when it happened.
What it is
From the CVE record
An 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'.
In plain language
Written by AI from the recordCVE-2019-1405 is a Windows security flaw that can let attackers gain higher system privileges; if your business uses affected Windows versions, you should act quickly because it has been used in real-world ransomware attacks.
CVE-2019-1405 is a Windows Universal Plug and Play (UPnP) elevation of privilege flaw (CWE-269) where the UPnP service improperly allows COM object creation, enabling attackers to run with higher privileges; it is listed in CISA KEV and was used in ransomware campaigns.
If you're affected
- Full server compromise
- Ransomware deployment risk
- User and admin account takeover
- Service disruption
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Listed as exploited in the wild since 2022-03-15.
US federal agencies must remediate by 2022-04-05.
Known use in ransomware campaigns.
Apply updates per vendor instructions.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
30% chance of exploitation activity in the next 30 days, which ranks it in the 98th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 128 days before any public exploit.
- Patch availablerecord updated
- OpenVAS check added
- EPSS band changehigh → moderate
- Public exploit / PoCsource: packetstorm
- Patch availablerecord updated
- Added to CISA KEVransomware campaign
Affected products
- Windows 7 Service Pack 1Operating Systems / windows
- Windows Server 2008 Service Pack 2 (Server Core Installation)Operating Systems / windows
- Windows 8.1Operating Systems / windows
- Windows Server 2012 (Server Core installation)Operating Systems / windows
- Windows Server 2012 R2 (Server Core installation)Operating Systems / windows
- Windows Server 2008 R2 Service Pack 1 (Server Core installation)Operating Systems / windows
- Windows 10 1607Operating Systems / windows
- Windows Server 2016 (Server Core installation)Operating Systems / windows
And 36 more affected products. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Scored 7.8 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Windows 7 Service Pack 1, not every advisory. This one: actively exploited.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI