dbcve.org
ChromeWeb browser · Google

CVE-2017-5080

HIGH · 8.8 CVSS v3.0 Published 2017-10-27
Fix available
A fix is available. Upgrade to 59.0.3071.86 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A use after free in credit card autofill in Google Chrome prior to 59.0.3071.86 for Linux and Windows allowed a remote attacker to perform an out of bounds memory read 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 confidence

A use-after-free vulnerability in Google Chrome's credit card autofill feature (versions prior to 59.0.3071.86 for Linux and Windows) allowed remote attackers to execute arbitrary code via a crafted HTML page. The vulnerability stems from the browser freeing memory during autofill operations but then continuing to access that freed memory, leading to out-of-bounds reads and potential code execution.

MitigationUpdate Google Chrome to version 59.0.3071.86 or later. Organizations should deploy the browser update via patch management systems and verify autofill functionality works correctly post-update.

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
Affected:< 59.0.3071.86

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine your Google Chrome version
    Open Chrome and navigate to chrome://version, or click the menu icon (three dots) > Help > About Google Chrome. Note the version number displayed.
    Affected if The displayed version is less than 59.0.3071.86 (for Linux or Windows)
  2. Check if credit card autofill is enabled
    Navigate to chrome://settings/autofill in the address bar, or go to Settings > Passwords and forms > Autofill settings. Look for the 'Credit cards' toggle or setting.
    Affected if Credit card autofill is turned ON (the toggle is enabled or the setting is checked)
  3. Confirm operating system
    Verify that Chrome is running on Linux or Windows (check System Preferences or the OS shown in chrome://version)
    Affected if The operating system is Linux or Windows

You are affected if your Chrome version is below 59.0.3071.86 AND you are running on Linux or Windows AND credit card autofill is enabled in your browser settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 59.0.3071.86 or later
Fixed in 59.0.3071.86
Interim mitigation

Update Google Chrome to version 59.0.3071.86 or later. Organizations should deploy the browser update via patch management systems and verify autofill functionality works correctly post-update.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5080 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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