Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2018-6065 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.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.
The vulnerability CVE-2018-6065 is an integer overflow (CWE-190) in the V8 JavaScript engine in Google Chrome versions prior to 65.0.3325.146. It occurs specifically when computing the required allocation size for instantiating a new JavaScript object and is rated 8.8 on CVSS 3.1 with a vector of AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
A remote attacker can exploit the flaw by delivering a crafted HTML page that triggers the integer overflow, resulting in heap corruption that may be leveraged for arbitrary code execution or other impacts on the affected browser process.
Vendor references, including the Chrome stable channel update, Red Hat RHSA-2018:0484, and Debian DSA-4182, indicate that the issue is resolved by upgrading to Chrome 65.0.3325.146 or later. The associated Chromium bug report provides additional technical context on the root cause in V8 allocation logic.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2018-17828
Vulnerability Data
Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- CWE(s)
- KEV Date Added
- 08 June 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
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 SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
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 can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.