dbcve.org
ChromeWeb browser · Google

CVE-2017-5045

MEDIUM · 6.1 CVSS v3.1 Published 2017-04-24
Fix available
A fix is available. Upgrade to after 57.0.2987.100 or later.
See remediation →
68/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
XSS Auditor in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android allowed detection of a blocked iframe load, which allowed a remote attacker to brute force JavaScript variables 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

The XSS Auditor in Chrome had an information disclosure vulnerability that allowed a remote attacker to detect when iframe loads were blocked, enabling brute-force enumeration of JavaScript variables via a crafted HTML page. This is a side-channel attack that bypasses the intended protection of the XSS Auditor.

MitigationUpdate Google Chrome to version 57.0.2987.98 or later (57.0.2987.108 for Android). No application-level code changes are required as this is a browser vulnerability.

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:<= 57.0.2987.75<= 57.0.2987.100
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:= 8.0= 9.0

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 on desktop
    Navigate to Chrome menu > Help > About Google Chrome, or navigate to chrome://version/ in the address bar. Note the 'Chrome' version number shown.
    Affected if The displayed version is 57.0.2987.75 or earlier, or is 57.0.2987.100 or earlier (versions 57.0.2987.76 through 57.0.2987.100 are affected). Versions 57.0.2987.98 and later (57.0.2987.108 for Android) are fixed.
  2. Check Chrome version via command line (Linux)
    Run 'google-chrome --version' or '/usr/bin/google-chrome --version' in a terminal. On RPM-based systems, also try 'rpm -q google-chrome'.
    Affected if The version output matches the affected ranges in step 1.
  3. Verify Chrome on RHEL/CentOS 6
    Check if Chrome is installed on Red Hat Enterprise Linux 6.0 Desktop/Server/Workstation by running 'rpm -qa | grep -i chrome' or checking /usr/bin/google-chrome existence.
    Affected if Chrome is installed and the version (if determinable) falls within the affected ranges.
  4. Verify Chrome on Debian Linux
    On Debian 8.0 or 9.0, run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' to check installed version.
    Affected if Chrome is installed and the version falls within affected ranges.

A user is affected if they are running Google Chrome version 57.0.2987.75 or earlier, or versions 57.0.2987.76 through 57.0.2987.100, on any desktop or Linux distribution listed.

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 a release after 57.0.2987.100
Interim mitigation

Update Google Chrome to version 57.0.2987.98 or later (57.0.2987.108 for Android). No application-level code changes are required as this is a browser vulnerability.

Fix this in Chrome 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-5045 — 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-5045 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