Skip to main content
Mallory
MediumVulnerability

CVE-2015-1285: Information disclosure in Chrome XSSAuditor canonicalize

Published Jul 23, 2015 · 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.4%73rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
GoogleDebian ProjectRed HatOpensuse
IdentifiersCVE-2015-1285CWE-203

CVE-2015-1285 is an information disclosure vulnerability in Blink's XSSAuditor, specifically in the XSSAuditor::canonicalize function as used by Google Chrome before 44.0.2403.89. The flaw is caused by improper selection of a truncation point during canonicalization, enabling an attacker to induce XSSAuditor false positives and then distinguish filtered from unfiltered responses through observable browser behavior. In practical exploitation, a remote attacker can frame a target page and infer whether the XSS filter activated by observing cross-origin accessible side effects such as changes in the framed document's structure, including a window.length value of 0 when filtering causes the content to become empty. This creates a linear-time oracle that can be used to test guesses about sensitive content present in the target response.

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 remote disclosure of sensitive information from cross-origin pages through side-channel observation of XSSAuditor activation. The issue does not directly provide script execution in the target origin, but it can let an attacker recover low-entropy secrets or other guessable sensitive values by iteratively probing the victim page and observing whether filtering occurred. The attack weakens browser same-origin protections by turning the XSS filter into a cross-origin detection oracle.

Mitigation

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

Where immediate patching is not possible, reduce exploitability by preventing attacker-controlled framing of sensitive pages and by minimizing exposure of guessable secrets in reflected or easily probeable response contexts. Applications with strong server-side XSS defenses may reduce risk by avoiding reliance on browser XSS filters and by using modern defensive controls such as Content Security Policy. Limiting cross-origin embedding and avoiding page structures whose observable properties change when content is blanked can also reduce available side channels, though these measures are compensating controls rather than complete fixes.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 44.0.2403.89 or later, which contains the vendor fix for CVE-2015-1285. Remediation should focus on removing the vulnerable XSSAuditor behavior in affected Blink-based builds by applying the vendor patch that corrects the canonicalization and truncation handling used during filter processing.

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
Debian ProjectDebian Linuxoperating_system
GoogleChromeapplication
OpensuseOpensuseoperating_system
Red HatEnterprise Linux Desktop Supplementaryoperating_system
Red HatEnterprise Linux Server Supplementaryoperating_system
Red HatEnterprise Linux Server Supplementary Eusoperating_system
Red HatEnterprise Linux Workstation Supplementaryoperating_system
FAQ

Frequently asked questions

Is CVE-2015-1285 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2015-1285 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2015-1285?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2015-1285.
Is there a patch for CVE-2015-1285?
Upgrade Google Chrome to version 44.0.2403.89 or later, which contains the vendor fix for CVE-2015-1285. Remediation should focus on removing the vulnerable XSSAuditor behavior in affected Blink-based builds by applying the vendor patch that corrects the canonicalization and truncation handling used during filter processing.
What products are affected by CVE-2015-1285?
Google Chrome, Debian Project Debian Linux, Red Hat Enterprise Linux Desktop Supplementary, Red Hat Enterprise Linux Server Supplementary, Red Hat Enterprise Linux Server Supplementary Eus, and 2 more.
How severe is CVE-2015-1285?
CVE-2015-1285 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 1.4% (73rd 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.