Skip to main content
Mallory
MediumVulnerability

CVE-2013-2848: Information disclosure in Google Chrome XSS Auditor

Published May 22, 2013 · 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%70th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Google
IdentifiersCVE-2013-2848CWE-200 · Exposure of Sensitive Information…

A vulnerability in Google Chrome's XSS Auditor before 27.0.1453.93 could allow remote attackers to obtain sensitive information through the browser's client-side XSS filtering behavior. The issue affected the browser's handling of detected XSS conditions and, in similar cases discussed for this bug class, filter activation could alter the loaded document state in a way that became observable across origins. CVE-2013-2848 has been described as an early Chrome information disclosure issue similar to later XSS Auditor side-channel flaws, with the filtered frame transitioning to an empty document state that could be distinguished from normal rendering. This created a cross-origin oracle that could be abused to infer secret values from otherwise non-vulnerable web applications by inducing false positives in the XSS filter and observing whether filtering occurred.

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 could disclose sensitive information from cross-origin pages to a remote attacker without requiring a conventional XSS vulnerability in the target application. The practical impact is limited to information that can be inferred through repeated probing and side-channel observation, typically low-entropy secrets or values that can be guessed incrementally. The vulnerability weakens the browser same-origin boundary by exposing whether specific reflected or embedded content triggered XSS Auditor logic.

Mitigation

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

Where immediate patching is not possible, reduce exploitability by preventing sensitive pages from being framed, minimizing reflection of attacker-controlled input into script contexts, and avoiding dependence on browser XSS filters as a primary defense. Strong application-layer XSS defenses and CSP can reduce exposure. If operationally appropriate, disabling legacy X-XSS-Protection behavior may avoid some filter-induced side channels, but suitability depends on the application's own XSS posture.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 27.0.1453.93 or later, where this issue was addressed. More broadly, reducing reliance on browser-side XSS filtering and using robust application-side output encoding and Content Security Policy provides a more reliable defense model than depending on XSS Auditor behavior.

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-2848 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2013-2848 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2013-2848?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2013-2848.
Is there a patch for CVE-2013-2848?
Upgrade Google Chrome to version 27.0.1453.93 or later, where this issue was addressed. More broadly, reducing reliance on browser-side XSS filtering and using robust application-side output encoding and Content Security Policy provides a more reliable defense model than depending on XSS Auditor behavior.
What products are affected by CVE-2013-2848?
Google Chrome.
How severe is CVE-2013-2848?
CVE-2013-2848 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 1.2% (70th 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.