dbcve.org
ChromeWeb browser · Google

CVE-2013-0909

MEDIUM · 5.0 CVSS v2.0 Published 2013-03-05
Fix available
A fix is available. Upgrade to after 25.0.1364.126 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The XSS Auditor in Google Chrome before 25.0.1364.152 allows remote attackers to obtain sensitive HTTP Referer information via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The XSS Auditor in Google Chrome before 25.0.1364.152 contained a flaw that allowed remote attackers to obtain sensitive HTTP Referer information via unspecified vectors. The XSS Auditor, meant to protect against cross-site scripting, could be tricked into disclosing Referer headers which may contain session tokens, private URLs, or other sensitive data.

MitigationUpdate Google Chrome to version 25.0.1364.152 or later. In enterprise environments, deploy the browser update via patch management or group policy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:<= 25.0.1364.126= 25.0.1364.0= 25.0.1364.1= 25.0.1364.2= 25.0.1364.3= 25.0.1364.5= 25.0.1364.7= 25.0.1364.8= 25.0.1364.9= 25.0.1364.10= 25.0.1364.11= 25.0.1364.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the browser is Google Chrome
    Open chrome://version and confirm the Product name field shows 'Google Chrome' (not Chromium or other variants).
    Affected if The browser is any variant other than Google Chrome (Chromium does not include the XSS Auditor).
  2. Check the installed Chrome version
    Open chrome://version and locate the 'Version' field, or open chrome://help to see the version number.
    Affected if The version is 25.0.1364.152 or lower, specifically versions <= 25.0.1364.126 or versions 25.0.1364.0 through 25.0.1364.12.
  3. Confirm XSS Auditor is enabled
    In older Chrome versions, the XSS Auditor could be controlled via the 'XSS Auditor' setting in chrome://settings or via group policy (under Computer Configuration/Administrative Templates/Google Chrome). Check if it is set to 'Enabled' or 'Default'.
    Affected if The XSS Auditor is enabled (the vulnerability only applies when this protection feature is turned on, as it is by default).

You are affected if you are running Google Chrome version 25.0.1364.152 or lower and the XSS Auditor is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 25.0.1364.126
Interim mitigation

Update Google Chrome to version 25.0.1364.152 or later. In enterprise environments, deploy the browser update via patch management or group policy.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0909 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0909 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data