CVE-2020-17087
Microsoft Windows 10 1507
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2020-17087 is a high-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Microsoft Windows 10 1507. 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 7% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2020-17087 is a Windows Kernel Local Elevation of Privilege Vulnerability affecting the Windows kernel. It is associated with CWE-131 and has a CVSS 3.1 score of 7.8 reflecting local attack vector, low attack complexity, and low privileges required.
An attacker with local access and low privileges can exploit the flaw without user interaction to obtain full elevation of privileges, resulting in high impact to confidentiality, integrity, and availability on the affected system.
Microsoft has published security guidance for the issue via its advisory portal, and the vulnerability appears in the CISA catalog of known exploited vulnerabilities.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-9042
Vulnerability Data
Windows Kernel Local Elevation of Privilege Vulnerability
- CWE(s)
- KEV Date Added
- 03 November 2021
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent buffer-size miscalculations via coding standards, reviews, and testing, while fixing this single weakness only partially fulfills the broader control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Training technical teams on secure coding practices (including buffer handling and integer overflow awareness) reduces but does not eliminate incorrect buffer size calculations; the defect is a specific arithmetic/implementation error that even trained developers commit, and the strongest control is testing (A.8.29), not training.
Secure coding standards directly require correct buffer-size calculations.
Security testing can detect buffer-size errors before release.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-131 is a regular software weakness introduced at implementation, the same class as CWE-134 which the owner graded `partial` for the same reason.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw, and CWE-131 commonly surfaces as CVEs in third-party components (font libraries, JavaScript engines, kernels), so the disclosed share is non-trivial; but the bulk of buffer-size calculation errors live in first-party custom code that never receives a CVE, and A.8.8's reach does not extend to source-reading tests on the organisation's own code (that is A.8.29's territory), leaving a nameable majority of instances outside its view.