ChromeWeb browser · Google
CVE-2018-17480
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExecution of user supplied Javascript during array deserialization leading to an out of bounds write in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA V8 JavaScript engine vulnerability in Google Chrome prior to version 71.0.3578.80 allows arbitrary code execution through an out-of-bounds write during array deserialization. A remote attacker can exploit this by tricking users into visiting a crafted HTML page that triggers the vulnerable deserialization path with user-controlled JavaScript.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 71.0.3578.80
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Chrome version on desktop systemsNavigate to chrome://settings/help in the browser address bar, or go to Help > About Google Chrome, to display the installed version numberAffected if The displayed version is earlier than 71.0.3578.80
-
Check Chrome version on Linux via command lineRun 'google-chrome --version' in a terminal, or inspect the package with 'rpm -q google-chrome' (RHEL) or 'dpkg -l google-chrome' (Debian)Affected if The reported version is earlier than 71.0.3578.80
-
Verify Chrome is present on the systemSearch for Chrome executables or check installed software inventory on the systemAffected if Google Chrome is installed and its version cannot be confirmed as 71.0.3578.80 or later
A user is affected if Google Chrome version is less than 71.0.3578.80, as the V8 array deserialization vulnerability exists in all prior versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped71.0.3578.80
Update Google Chrome to version 71.0.3578.80 or later to patch the V8 engine vulnerability.
Chrome 71.0.3578.80 or later
- 1. Open Google Chrome on the affected system
- 2. Click the menu icon (three dots) in the top-right corner
- 3. Select 'Help' and then 'About Google Chrome'
- 4. The browser will check for updates automatically
- 5. If an update is available, click 'Update Google Chrome'
- 6. Restart the browser to apply the update
- 7. Verify the version is 71.0.3578.80 or later via the same About dialog
- For Enterprise Linux/Debian systems using system package managers, run: yum update google-chrome-stable or apt-get update && apt-get upgrade google-chrome-stable
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-17480 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data