CVE-2014-3197: Information disclosure in Chrome XSSAuditor block mode
- Vendors
- GoogleRed Hat
CVE-2014-3197 is an information disclosure vulnerability in Blink's NavigationScheduler::schedulePageBlock function, as used by Google Chrome before 38.0.2125.101. When Chrome's XSSAuditor blocked a page in X-XSS-Protection block mode after detecting a reflected-XSS pattern, the browser did not correctly provide substitute data for the blocked page. Instead, the blocked navigation exposed a detectable state change, including replacement behavior associated with a data: URL, that could be observed cross-origin. A remote attacker could induce false positives in the XSS filter using crafted web content and then test guessed values embedded in requests to a target page. By observing whether the filter activated for each guess, the attacker could infer sensitive information present in the target response, particularly low-entropy secrets reflected early in script content. The issue is therefore not a same-origin policy bypass in the classic sense, but a cross-origin side channel created by XSS filter block-mode handling.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote disclosure of sensitive information from a cross-origin page that would not otherwise be readable by the attacker. The attack enables trial-and-error extraction of low-entropy secret values by distinguishing filtered from unfiltered responses through browser-observable side effects. This can undermine confidentiality protections for reflected secrets in affected pages even when the target application has no exploitable XSS vulnerability of its own.
Mitigation
If you can’t patch tonight, do this now.
Reduce exposure by disabling or avoiding reliance on browser XSS filter behavior where application-side XSS defenses are strong, and prefer robust server-side output encoding and Content Security Policy. Prevent framing of sensitive pages where feasible, avoid reflecting secrets into script blocks, and avoid placing sensitive reflected values in positions that can be influenced by request/response matching heuristics. These measures can reduce exploitability but do not replace patching the browser.
Remediation
Patch, then assume compromise.
Upgrade Google Chrome to version 38.0.2125.101 or later. The vendor fix preserved the original page URL and corrected blocked-page handling so that XSSAuditor activation no longer exposed a distinguishable cross-origin signal through substitute-data behavior.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2014-3197 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2014-3197 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2014-3197?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2014-3197.
- Is there a patch for CVE-2014-3197?
- Upgrade Google Chrome to version 38.0.2125.101 or later. The vendor fix preserved the original page URL and corrected blocked-page handling so that XSSAuditor activation no longer exposed a distinguishable cross-origin signal through substitute-data behavior.
- What products are affected by CVE-2014-3197?
- Google Chrome, Red Hat Enterprise Linux Desktop Supplementary, Red Hat Enterprise Linux Server Supplementary, Red Hat Enterprise Linux Server Supplementary Eus, and Red Hat Enterprise Linux Workstation Supplementary.
- How severe is CVE-2014-3197?
- CVE-2014-3197 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 1.0% (64th percentile) as of Oct 16, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.