ChromeWeb browser · Google
CVE-2013-0904
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 · uneditedThe Web Audio implementation in Google Chrome before 25.0.1364.152 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown 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 · moderate confidenceMemory corruption vulnerability in Google Chrome's Web Audio API implementation affecting versions prior to 25.0.1364.152. The flaw allows remote attackers to cause denial of service or potentially achieve unspecified code execution via unknown attack vectors.
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
<= 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.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Chrome executable: on Windows look in Program Files/Google/Chrome/Application/ or run 'chrome --version' from command line; on Mac check /Applications/Google Chrome.app; on Linux run 'google-chrome --version' or check /usr/bin/google-chromeAffected if Google Chrome browser is present on the system
-
Determine installed Chrome version numberNavigate to chrome://version in the Chrome address bar, or run 'google-chrome --version' from terminal/command prompt, or check the version property of the Chrome executableAffected if The displayed version is 25.0.1364.126 or lower, or matches any of these specific versions: 25.0.1364.0 through 25.0.1364.12
-
Compare version against affected rangeCompare your installed version (from step 2) against the affected versions: any version <= 25.0.1364.126 OR exactly 25.0.1364.0 through 25.0.1364.12 are vulnerableAffected if The installed version falls within the affected range and has not been updated to 25.0.1364.152 or later
-
Confirm Web Audio API usage (optional context)Check if any web applications or extensions loaded in Chrome actively use the Web Audio API by inspecting browser developer tools console or network activity, or review enterprise web applications for Web Audio API callsAffected if Web Audio API is actively used in your Chrome browser sessions; however the vulnerability may still trigger regardless of active use when processing malicious web content
You are affected if Google Chrome version is 25.0.1364.126 or lower, or exactly 25.0.1364.0 through 25.0.1364.12, and the browser processes untrusted web content using the Web Audio API.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Google Chrome to version 25.0.1364.152 or later. In enterprise environments, deploy the update via centralized patch management and verify successful installation across affected endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0904 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0904 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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