CVE-2020-16009
Memory Safety in Opensuse Backports Sle 15.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2020-16009 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Opensuse Backports Sle. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 1% 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.
The vulnerability is an inappropriate implementation in the V8 JavaScript engine within Google Chrome versions prior to 86.0.4240.183. It is associated with CWE-787 (out-of-bounds write) and CWE-843 (type confusion) and can result in heap corruption when a victim visits a crafted HTML page. The issue received a CVSS 3.1 base score of 8.8.
A remote attacker can exploit the flaw by serving a malicious HTML page that triggers the corruption. Successful exploitation grants the attacker confidentiality, integrity, and availability impacts without requiring authentication or special privileges beyond convincing the user to visit the page.
Chrome release notes and distribution advisories direct users to upgrade to version 86.0.4240.183 or later; corresponding OpenSUSE updates were published to address the same component. Public references also include a proof-of-concept targeting V8's Turbofan JIT compiler via type confusion.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-1500
Vulnerability Data
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- CWE(s)
- KEV Date Added
- 03 November 2021
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.5.2V15.3.5
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.
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.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
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.