Security readout for executives and security teams
Plain-English summary
A malicious web page could trigger memory corruption in older Google Chrome versions. Organizations still running Chrome or Chromium builds before 62.0.3202.62 should treat this as a browser patching issue, especially on systems exposed to general web browsing.
Executive priority
Prioritize remediation if any legacy Chrome or Chromium builds remain in use. Modern managed browsers are likely already fixed, but unmanaged endpoints, old gold images, and embedded browsing systems can preserve exposure years later.
Technical view
CVE-2017-5128 is a heap buffer overflow in Blink related to WebGL in Google Chrome before 62.0.3202.62. The described attack vector is a crafted HTML page causing potential heap corruption. The source bundle does not provide CVSS, CWE, or detailed root-cause data.
Likely exposure
Exposure is likely limited to endpoints or managed images running Google Chrome prior to 62.0.3202.62, or affected downstream Chromium packages covered by Debian, Red Hat, or Gentoo advisories.
Exploitation context
The bundle does not cite active exploitation, and the CVE is not marked KEV. The documented scenario is remote delivery through crafted HTML content related to WebGL, but no exploit details are provided in the supplied sources.
Researcher notes
The strongest evidence is the Chrome stable update and Linux vendor advisories. The public bundle names Blink, WebGL, heap buffer overflow, crafted HTML, and the fixed Chrome version, but lacks exploitability details, CVSS scoring, and unrestricted Chromium bug context.
Mitigation direction
- Upgrade Google Chrome to 62.0.3202.62 or later.
- Apply relevant Debian, Red Hat, or Gentoo Chromium security updates.
- Retire or isolate systems unable to update affected browser builds.
- Check current vendor guidance for any platform-specific package status.
Validation and detection
- Inventory Chrome and Chromium versions across managed endpoints.
- Confirm browser versions are 62.0.3202.62 or later.
- Verify Linux package updates align with the cited vendor advisories.
- Check legacy images and kiosks for pinned outdated browser builds.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-5128 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.htmlCVE reference · x_refsource_MISC
- DSA-4020CVE reference · vendor-advisory, x_refsource_DEBIAN
- RHSA-2017:2997CVE reference · vendor-advisory, x_refsource_REDHAT
- https://crbug.com/765469CVE reference · x_refsource_MISC
- GLSA-201710-24CVE reference · vendor-advisory, x_refsource_GENTOO
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.