Skip to main content
Mallory
MediumVulnerability

CVE-2013-6656: Information Disclosure in Chrome Blink XSSAuditor Redirect Handling

Published Feb 24, 2014 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS1.2%68th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Google
IdentifiersCVE-2013-6656CWE-200 · Exposure of Sensitive Information…

CVE-2013-6656 is an information disclosure vulnerability in Blink's XSSAuditor implementation in Google Chrome prior to 33.0.1750.117. The flaw is in the XSSAuditor::init function in core/html/parser/XSSAuditor.cpp when processing POST requests that involve redirection. Instead of correlating the POST body with the redirect target, the auditor incorrectly uses the body of the redirecting page. This request/response mismatch can cause the browser-side XSS filter to make security decisions based on the wrong request context. A remote attacker can abuse this behavior to trigger detectable filter behavior and infer sensitive information, including POST parameter values, through unspecified vectors.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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 cross-origin disclosure of sensitive information by abusing browser XSS filter behavior rather than a direct flaw in the target web application. The vulnerability can enable an attacker to infer or recover secret values associated with POST requests, undermining origin boundaries and exposing data that should not be readable by an attacker-controlled site.

Mitigation

If you can’t patch tonight, do this now.

Where immediate patching is not possible, reduce exposure by disabling or avoiding reliance on browser XSS filtering behavior in sensitive workflows, and prefer application-layer defenses such as robust server-side output encoding and Content Security Policy. Limiting cross-origin framing and minimizing exposure of sensitive low-entropy values in contexts that can be reflected into XSS filter matching logic may also reduce exploitability, but these are compensating controls rather than complete fixes.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 33.0.1750.117 or later, where the XSSAuditor redirect-handling issue was fixed. Applying the vendor-provided browser update is the primary remediation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2013-6656 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-6656 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-6656?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2013-6656.
Is there a patch for CVE-2013-6656?
Upgrade Google Chrome to version 33.0.1750.117 or later, where the XSSAuditor redirect-handling issue was fixed. Applying the vendor-provided browser update is the primary remediation.
What products are affected by CVE-2013-6656?
Google Chrome.
How severe is CVE-2013-6656?
CVE-2013-6656 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 1.2% (68th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.