dbcve.org
Enterprise Linux DesktopOperating system · Redhat

CVE-2017-15416

MEDIUM · 6.5 CVSS v3.0 Published 2018-08-28
Fix available
A fix is available. Upgrade to 63.0.3239.84 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Heap buffer overflow in Blob API in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page, aka a Blink out-of-bounds read.

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

Heap buffer overflow in Google Chrome's Blob API (Blink rendering engine) prior to version 63.0.3239.84 allows a remote attacker to potentially exploit heap corruption via a crafted HTML page containing malicious Blob operations.

MitigationUpdate Google Chrome to version 63.0.3239.84 or later to obtain the patched build; no additional configuration changes required.

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
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Debian LinuxOperating system
Affected:= 9.0
ChromeWeb browser
Affected:< 63.0.3239.84

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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Check Google Chrome version
    Open Chrome, click the menu icon (three dots), select Help, then About Google Chrome. Alternatively, navigate to chrome://settings/help in the address bar.
    Affected if The displayed version number is less than 63.0.3239.84 (for example, 63.0.3239.83 or earlier)
  2. Verify Chrome installation on Linux
    Run 'google-chrome --version' or 'chromium-browser --version' in the terminal.
    Affected if The reported version is less than 63.0.3239.84
  3. Confirm Blob API is accessible
    The Blob API is a standard browser API enabled by default in Chrome. No manual configuration needed - the vulnerability triggers simply by visiting a webpage with malicious Blob operations.
    Affected if Chrome version is below 63.0.3239.84 AND the browser is used to render untrusted web content

You are affected if Google Chrome version is below 63.0.3239.84 (or the corresponding patched version for your distribution) and you use Chrome to browse web pages.

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 63.0.3239.84 or later
Fixed in 63.0.3239.84
Interim mitigation

Update Google Chrome to version 63.0.3239.84 or later to obtain the patched build; no additional configuration changes required.

Fix this in Enterprise Linux Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15416 — 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-15416 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