ChromeWeb browser · Google
CVE-2017-15423
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 · uneditedInappropriate implementation in BoringSSL SPAKE2 in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to leak the low-order bits of SHA512(password) by inspecting protocol traffic.
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 confidenceA cryptographic implementation flaw in BoringSSL's SPAKE2 protocol within Google Chrome versions prior to 63.0.3239.84 allowed remote attackers to leak the low-order bits of SHA512(password) through passive inspection of protocol traffic. The vulnerability stems from inappropriate implementation of the SPAKE2 password-authenticated key exchange, not from SHA512 itself.
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
< 63.0.3239.84
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to view the installed Chrome versionAffected if The version is lower than 63.0.3239.84
-
Confirm SPAKE2 protocol is in useInspect active browser connections or proxy logs for SPAKE2-based password-authenticated key exchange (PAKE) traffic - look for SPAKE2 messages in network capturesAffected if The browser is actively using SPAKE2 for any password-authenticated connections
-
Check for vulnerable BoringSSL libraryOn systems with bundled BoringSSL (such as certain Linux distributions), inspect the BoringSSL library version used by Chrome: locate libboringssl.so or similar and query its version metadataAffected if The bundled BoringSSL library predates the fix and SPAKE2 is in use
A user is affected if their Google Chrome version is below 63.0.3239.84 AND they are using SPAKE2-based password-authenticated connections where an attacker can passively inspect network traffic.
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 data63.0.3239.84
Update Google Chrome to version 63.0.3239.84 or later to receive the patched BoringSSL implementation. This is a client-side vulnerability requiring browser updates; server-side mitigations do not apply.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15423 — 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-15423 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