dbcve.org
Chrome OsOperating system · Google

CVE-2017-15397

HIGH · 7.4 CVSS v3.0 Published 2018-02-07
Fix available
A fix is available. Upgrade to 62.0.3202.74 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Inappropriate implementation in ChromeVox in Google Chrome OS prior to 62.0.3202.74 allowed a remote attacker in a privileged network position to observe or tamper with certain cleartext HTTP requests by leveraging that position.

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

ChromeVox (Chrome OS screen reader) had an implementation flaw where certain HTTP requests were transmitted in cleartext, allowing a network-attacker in a privileged position to intercept or modify these requests via man-in-the-middle attacks.

MitigationUpdate Chrome OS to version 62.0.3202.74 or later to obtain the patch; avoid transmitting sensitive data over cleartext HTTP on untrusted networks.

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
Chrome OsOperating system
Affected:< 62.0.3202.74

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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. Check Chrome OS version
    Open Chrome browser, navigate to chrome://settings/help, or go to Settings > About Chrome OS to view the current version number
    Affected if The installed version is lower than 62.0.3202.74 (e.g., 62.0.3202.59 or earlier)
  2. Confirm ChromeVox is enabled
    Open Chrome OS Settings, search for 'Accessibility', and verify if ChromeVox (screen reader) is turned on
    Affected if ChromeVox is enabled and the Chrome OS version is below 62.0.3202.74
  3. Identify cleartext HTTP requests
    Use Chrome DevTools Network tab or a network packet capture tool while ChromeVox is active to observe if any HTTP (not HTTPS) requests are being made
    Affected if Any HTTP requests are transmitted in cleartext while using ChromeVox on a version below 62.0.3202.74

You are affected if Chrome OS version is below 62.0.3202.74 AND ChromeVox screen reader is enabled and actively transmitting HTTP requests in cleartext.

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

Update Chrome OS to version 62.0.3202.74 or later to obtain the patch; avoid transmitting sensitive data over cleartext HTTP on untrusted networks.

Fix this in Chrome Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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