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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
ChromeのXSSフィルタを使って応答内容ではなくPOSTパラメータ値を窃取する攻撃として紹介される情報漏えい脆弱性の一つ。
A Chrome XSS filter information disclosure vulnerability described as enabling exfiltration of POST parameter values rather than response content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.