CVE-2017-5022: n/a Google Chrome prior to 56.0.2924.76 for Linux,…

CVE-2017-5022: Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, fail...

Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to properly enforce unsafe-inline content security policy, which allowed a remote attacker to bypass content security policy via a crafted HTML page.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 14:47 UTC (UTC+00:00)

Security readout for executives and security teams

This Chrome flaw weakened a browser safety control. A crafted web page could bypass Content Security Policy handling around unsafe-inline, reducing protection against injected script in sites that relied on CSP. The practical business risk is concentrated in unmanaged or legacy Chrome installations from early 2017. Exposure is likely limited to endpoints, virtual desktops, or Android devices still running the listed pre-56 Chrome versions. Modern managed Chrome fleets should already be remediated unless update controls failed or legacy systems remain in use. Treat this as a legacy browser hygiene issue unless affected Chrome versions still exist. Prioritize discovery and forced update on unmanaged endpoints, kiosks, VDI images, and old Android devices. Mitigation focus: Update Chrome to at least the fixed versions listed by Google.; Apply relevant Gentoo, Red Hat, or Debian browser package advisories.; Remove unsupported Chrome versions from managed endpoints and golden images..

Prepared: Jun 13, 2026, 06:20 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2017-5022 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Feb 17, 2017, 07:45 UTC (UTC+00:00)

Official CVE source material

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.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

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/01/stable-channel-update-for-desktop.htmlCVE reference · x_refsource_CONFIRM
GLSA-201701-66CVE reference · vendor-advisory, x_refsource_GENTOO
https://crbug.com/663620CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/aGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for AndroidGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for AndroidListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.