Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2020-1027 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Microsoft Windows 10 1709. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 9% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
An elevation of privilege vulnerability exists in the Windows Kernel due to improper handling of objects in memory, tracked as CVE-2020-1027 and assigned CWE-787 for out-of-bounds write. The flaw affects the Windows operating system kernel and is distinct from related issues such as CVE-2020-0913, CVE-2020-1000, and CVE-2020-1003. It carries a CVSS 3.1 base score of 7.8 reflecting local attack vector, low complexity, and low privileges required.
A local attacker with existing low-privileged access on a vulnerable system can exploit the flaw to corrupt kernel memory structures, resulting in arbitrary code execution with full system privileges that allow complete control over confidentiality, integrity, and availability of the host.
Microsoft has published guidance and security updates addressing the issue through its Security Response Center advisory, while the vulnerability appears in CISA's catalog of known exploited vulnerabilities in the wild. Public proof-of-concept material references a heap buffer overflow path involving sxs.dll XML parsing of assembly identity elements.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-11922
Vulnerability Data
An elevation of privilege vulnerability exists in the way that the Windows Kernel handles objects in memory, aka 'Windows Kernel Elevation of Privilege Vulnerability'. This CVE ID is unique from CVE-2020-0913, CVE-2020-1000, CVE-2020-1003.
- CWE(s)
- KEV Date Added
- 23 May 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.