dbcve.org
ChromeWeb browser · Google

CVE-2013-0905

HIGH · 7.5 CVSS v2.0 Published 2013-03-05
Fix available
A fix is available. Upgrade to after 25.0.1364.126 or later.
See remediation →
84/100
Remediation priority · High
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
Use-after-free vulnerability in Google Chrome before 25.0.1364.152 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving an SVG animation.

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

A use-after-free vulnerability in Google Chrome versions prior to 25.0.1364.152 allows remote attackers to free memory and then access it again (use-after-free) via crafted SVG animation vectors. This memory corruption can lead to denial of service or potentially enable arbitrary code execution.

MitigationUpgrade Google Chrome to version 25.0.1364.152 or later to obtain the patched version that addresses this use-after-free vulnerability in the SVG animation handling component.

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
Partial
Availability
Partial

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

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. Check installed Chrome version
    Open Chrome and navigate to chrome://version, or on Windows check Help > About Google Chrome, or run 'google-chrome --version' on Linux, or 'Google Chrome.app/Contents/MacOS/Google Chrome --version' on macOS
    Affected if The version displayed is 25.0.1364.126 or earlier, OR is exactly one of these: 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, or 25.0.1364.12
  2. Verify SVG animation handling is enabled
    Navigate to chrome://settings in Chrome and search for SVG settings, or inspect that SVG rendering is not disabled via enterprise policy. By default SVG is fully enabled in Chrome.
    Affected if SVG rendering is enabled (this is the default and required condition for the vulnerability to be triggerable)
  3. Confirm Chrome is used as the browser
    Verify that the browser in use is Google Chrome and not Chromium or another Chromium-based browser, as this CVE specifically affects Google Chrome builds
    Affected if The browser is Google Chrome (not plain Chromium or other browsers)

You are affected if your Google Chrome version falls within 25.0.1364.0 through 25.0.1364.12 (excluding .152) or is 25.0.1364.126 or earlier, and SVG animation support is enabled (the default state).

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

Upgrade Google Chrome to version 25.0.1364.152 or later to obtain the patched version that addresses this use-after-free vulnerability in the SVG animation handling component.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0905 — 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-0905 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