CVE-2016-2845: n/a vulnerability

CVE-2016-2845: The Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 49.0.2623.75, do...

The Content Security Policy (CSP) implementation in Blink, as used in Google Chrome before 49.0.2623.75, does not ignore a URL's path component in the case of a ServiceWorker fetch, which allows remote attackers to obtain sensitive information about visited web pages by reading CSP violation reports, related to FrameFetchContext.cpp and ResourceFetcher.cpp.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 23:32 UTC (UTC+00:00)

Security readout for executives and security teams

This is a browser privacy flaw in Chrome’s Blink engine before version 49.0.2623.75. A malicious site could infer sensitive information about pages a user had visited by abusing CSP violation reports during ServiceWorker fetch behavior. Business risk is mainly legacy browser exposure, not server compromise. Exposure is most likely where users still run Chrome or Chromium builds older than 49.0.2623.75, including unmanaged endpoints, kiosks, legacy virtual desktops, or old Linux packages. The supplied affected-product metadata is incomplete, so confirm against browser inventory rather than assuming broader product impact. Treat this as a legacy-browser hygiene issue with privacy implications. It deserves remediation if old Chrome or Chromium exists in the environment, but the provided evidence does not justify emergency response absent confirmed affected assets or active exploitation. Mitigation focus: Upgrade Chrome or Chromium to 49.0.2623.75 or later.; Remove unsupported legacy browser builds from managed endpoints.; Check Ubuntu or OS vendor advisories for packaged Chromium updates..

Prepared: Jun 13, 2026, 21:06 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-2016-2845 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: Mar 6, 2016, 02:00 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://codereview.chromium.org/1454003003/CVE reference · x_refsource_CONFIRM
https://code.google.com/p/chromium/issues/detail?id=591402CVE reference · x_refsource_CONFIRM
https://bugs.chromium.org/p/chromium/issues/detail?id=542060CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

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