PatchSiren cyber security CVE debrief
CVE-2017-5012 Google CVE debrief
CVE-2017-5012 is a high-severity Google Chrome vulnerability disclosed on 2017-02-17. According to NVD, a crafted HTML page could trigger a heap buffer overflow in V8 and lead to heap corruption in affected Chrome versions.
- Vendor
- Product
- Chrome
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2017-02-17
- Original CVE updated
- 2026-05-13
- Advisory published
- 2017-02-17
- Advisory updated
- 2026-05-13
Who should care
Browser security teams, endpoint administrators, and anyone managing Google Chrome on Linux, Windows, macOS, or Android should care—especially environments that lag on browser updates or rely on managed, downstream-packaged builds.
Technical summary
NVD describes this issue as a heap buffer overflow in the V8 engine used by Google Chrome. The attack vector is network-based and requires user interaction, consistent with a crafted HTML page reaching the vulnerable code path and causing heap corruption. The supplied NVD record lists Chrome versions through 55.0.2883.87 in its CPE criteria, while the CVE description states fixes were available in 56.0.2924.76 for Linux/Windows/Mac and 56.0.2924.87 for Android.
Defensive priority
High. This is a remotely reachable browser memory-corruption flaw with high CVSS impact and should be remediated quickly across all managed Chrome deployments.
Recommended defensive actions
- Update Google Chrome to a fixed release: 56.0.2924.76 on Linux, Windows, and Mac, or 56.0.2924.87 on Android.
- Verify installed browser versions across managed endpoints, kiosks, and VDI fleets; treat any vulnerable build as needing remediation.
- Check downstream vendor advisories for packaged Chrome builds and apply the corresponding enterprise or distribution update.
- Prioritize systems that frequently browse untrusted content or that do not receive automatic browser updates in a timely way.
- Use the Google Chrome release notes and vendor advisories to confirm remediation and deployment status.
Evidence notes
All factual statements are grounded in the supplied NVD record and its listed references. The NVD description identifies a V8 heap buffer overflow triggered by a crafted HTML page; the CVSS vector is CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H and the weakness is CWE-119. The reference set includes Google's Chrome release note, the Chromium bug entry, and downstream advisories from Red Hat, Debian, and Gentoo. Note that the NVD CPE criteria and prose description do not present exactly the same version boundary, so precise patch verification should rely on the vendor release notes and downstream advisories.
Sources and references
Verified primary and authoritative sources
-
CVE-2017-5012 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2017-5012
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2017-5012 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2017-5012
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html
-
Source reference
Unverified legacy reference
URL: https://crbug.com/681843
-
Source reference
Unverified legacy reference
URL: https://security.gentoo.org/glsa/201701-66
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.