ChromeWeb browser · Google
CVE-2017-5069
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 · uneditedIncorrect MIME type of XSS-Protection reports in Blink in Google Chrome prior to 58.0.3029.81 for Linux, Windows, and Mac, and 58.0.3029.83 for Android, allowed a remote attacker to circumvent Cross-Origin Resource Sharing checks 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 confidenceIn Blink (Chrome's rendering engine), XSS-Protection reports were being sent with an incorrect MIME type. This allowed a remote attacker to craft malicious HTML pages that could circumvent Cross-Origin Resource Sharing (CORS) checks, potentially enabling unauthorized cross-origin data access.
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
< 58.0.3029.81< 58.0.3029.83
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome version on desktop systemsOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command line to display the installed version numberAffected if Version is below 58.0.3029.81 (Windows/Mac/Linux) or below 58.0.3029.83 (Android)
-
Verify if XSS protection is enabled in ChromeNavigate to chrome://settings/security (or chrome://flags/#xss-auditor on older versions) and check whether the XSS auditor is turned on or set to defaultAffected if XSS protection is enabled (the vulnerability only applies when this feature is active, as it concerns the MIME type of XSS-Protection reports)
-
Check for Chrome installation on RHEL 6.0 systemsOn Red Hat Enterprise Linux 6.0 desktop, server, or workstation, run 'rpm -q google-chrome' or 'rpm -qa | grep chrome' to list any installed Chrome packagesAffected if Google Chrome is installed on RHEL 6.0 (the specific version on RHEL 6.0 falls within the affected range)
-
Inspect Chrome executable path and version on Linux systemsRun 'which google-chrome' to locate the executable, then run 'google-chrome --version' or check the package info via 'rpm -qi <package-name>'Affected if The installed Chrome version is below 58.0.3029.81
You are affected if Google Chrome (desktop or Android) version is below 58.0.3029.81/58.0.3029.83 respectively, and XSS protection feature is enabled in the browser settings.
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.
From vendor data58.0.3029.8158.0.3029.83
Update Google Chrome to version 58.0.3029.81 or later (desktop) or 58.0.3029.83 or later (Android) to receive the patched Blink rendering engine with correct MIME type handling for XSS-Protection reports.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-2017-5069 — 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-2017-5069 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