A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a
A security feature bypass vulnerability exists when Windows fails to properly handle token relationships.An attacker who successfully exploited the vulnerability could allow an application with a certain integrity level to execute code at a different integrity level, leading to a sandbox escape.The update addresses the vulnerability by correcting how Windows handles token relationships, aka…
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Windows 10 Version 1909 for 32 | bit Systems — unspecified |
| Microsoft | Windows 10 Version 1909 for x64 | based Systems — unspecified |
| Microsoft | Windows 10 Version 1909 for ARM64 | based Systems — unspecified |
| Microsoft | Windows Server, version 1909 (Server Core installation) | unspecified |
| Microsoft | Windows 10 Version 1903 for 32 | bit Systems — unspecified |
| Microsoft | Windows 10 Version 1903 for x64 | based Systems — unspecified |
| Microsoft | Windows 10 Version 1903 for ARM64 | based Systems — unspecified |
| Microsoft | Windows Server, version 1903 (Server Core installation) | unspecified |
Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.
For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.
Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.
No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.