Skip to main content
Mallory
← Back to News
endpoint-software-vulnerabilityinternet-facing-service-vulnerability

Browser XSS Filters Enabled Cross-Origin Information Theft and UXSS

Vulnerability Disclosure · 8 sources · Updated 3mo ago · First seen Aug 15, 2026

Browser XSS Filters Enabled Cross-Origin Information Theft and UXSS

Research from Mitsui Bussan Secure Directions detailed how browser XSS filters in Chrome and Internet Explorer introduced exploitable behavior that let attackers steal information or trigger universal cross-site scripting, even when the target web application had no native XSS flaw. The write-up tied the issue to historical cases including CVE-2014-3197, CVE-2015-1285, CVE-2013-2848, CVE-2013-6656, CVE-2013-6657, CVE-2011-1992, and CVE-2009-4047, showing that request/response matching and response rewriting by the browser could create false positives that attackers then abused.

The attacks relied on detecting whether the filter activated through side channels such as URL changes, timing differences, CSP reports, or window.length, allowing low-entropy secrets to be inferred across origins. A related Chromium security issue documented an XSS-filter information leak, while the broader analysis concluded that neither normal mode nor block mode is universally safe because each creates different tradeoffs; the recommended priority is strong application-side XSS prevention and use of CSP, with disabling browser XSS filters considered for applications that already have robust native defenses.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

11 events · 2008 – Dec 2015
  1. Reported Apr 7, 201611y ago

    Google mitigates CVE-2014-3197 by preserving the original URL

    Google fixed the Chrome CVE-2014-3197 issue by preserving the original page URL when the XSS filter triggered, preventing attackers from detecting activation through URL changes. The references also note Apple applied the same mitigation to a similar Safari bug.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  2. Dec 2015

    Microsoft issues an incomplete update for Kinugawa's IE filter findings

    The references state that Microsoft's December 2015 update for Kinugawa's reported Internet Explorer filter issues addressed only part of the reported methods. This left some concern that the remediation was incomplete.

    Information theft attacks abusing browser's XSS filter | 技術者ブログ | 三井物産セキュアディレクション株式会社
  3. 2015

    Masato Kinugawa reports IE UXSS flaws CVE-2015-6144 and CVE-2015-6176

    Masato Kinugawa reported Internet Explorer UXSS issues CVE-2015-6144 and CVE-2015-6176, which the references say reproduced in normal mode rather than block mode. These findings reinforced the risk of partial response rewriting by browser XSS filters.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  4. 2015

    Gareth Heyes reports Chrome CVE-2015-1285 side-channel leak

    Gareth Heyes reported Chrome CVE-2015-1285, an information disclosure attack that inferred XSS filter activation through cross-origin reads of window.length. In the vulnerable behavior, filtered framed content became empty, making window.length drop to 0.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  5. 2014

    Microsoft recognizes IE XSS filter bypass CVE-2014-6328

    The references cite CVE-2014-6328 as an example of a pure Internet Explorer XSS filter bypass that Microsoft treated as a vulnerability. This is presented as evidence that some browser vendors formally tracked filter bypasses as security issues.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  6. 2014

    Takeshi Terada reports Chrome XSS filter leak CVE-2014-3197

    Takeshi Terada reported Chrome CVE-2014-3197, an information disclosure vulnerability that let attackers infer secret values from cross-origin pages by deliberately triggering false positives in Chrome's XSS filter. The Chromium issue reference was published on 2014-07-23, but the content anchors the event only to 2014.

    Security: XSS filter information leak [40080096] - Chromium
  7. 2013

    Chrome CVE-2013-6656 and CVE-2013-6657 target POST data theft

    NeeXEmil reported Chrome CVE-2013-6656 and CVE-2013-6657, which abused XSS filter behavior to steal POST parameter values rather than response content. These cases expanded the known impact of XSS-filter-based information leakage.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  8. 2013

    Chrome CVE-2013-2848 reveals cross-origin data via XSS filter behavior

    Egor Homakov reported Chrome CVE-2013-2848, an earlier information disclosure issue similar to later Chrome XSS filter leaks. The references say it exposed filter activation through a navigation change to about:blank.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  9. 2011

    IE CVE-2011-1992 enables XSS-filter-based information disclosure

    Thomas Stehle reported Internet Explorer CVE-2011-1992, an information disclosure issue in which attackers could infer cross-domain or cross-zone content through trial and error. The attack relied on partial matches and timing differences in the filter's regex processing to recover secret characters.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  10. 2009

    IE CVE-2009-4047 exposes UXSS risk from XSS filter rewriting

    Internet Explorer vulnerability CVE-2009-4047 showed that XSS filter response rewriting could create universal XSS even when the target application had no XSS flaw. The references say Microsoft introduced X-XSS-Protection: 1; mode=block after this issue to avoid partial rewriting.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
  11. 2008

    Internet Explorer 8 introduces a built-in XSS filter

    Microsoft first implemented a browser XSS filter in Internet Explorer 8. The references anchor this introduction to 2008 and describe it as an early built-in, best-effort XSS defense.

    ブラウザのXSSフィルタを利用した情報窃取攻撃 | 技術者ブログ | 三井物産セキュアディレクション株式会社
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.