ChromeWeb browser · Google
CVE-2013-2917
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 ReverbConvolverStage::ReverbConvolverStage function in core/platform/audio/ReverbConvolverStage.cpp in the Web Audio implementation in Blink, as used in Google Chrome before 30.0.1599.66, allows remote attackers to cause a denial of service (out-of-bounds read) via vectors related to the impulseResponse array.
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 confidenceOut-of-bounds read vulnerability in the Web Audio API's ReverbConvolverStage component in Blink. The issue occurs in the ReverbConvolverStage constructor when processing the impulseResponse array, allowing remote attackers to cause a denial of service via crafted audio content.
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
<= 30.0.1599.65= 30.0.1599.0= 30.0.1599.1= 30.0.1599.2= 30.0.1599.4= 30.0.1599.5= 30.0.1599.6= 30.0.1599.7= 30.0.1599.8= 30.0.1599.9= 30.0.1599.10= 30.0.1599.11CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify the browser vendor and versionNavigate to chrome://version or check About Chrome in the menu to see the full version string (for example, 30.0.1599.65)Affected if The browser is Google Chrome or a Chromium-based browser and the version matches 30.0.1599.0 through 30.0.1599.65, or any of the specifically listed versions (30.0.1599.0-30.0.1599.11)
-
Confirm browser is Chromium-basedCheck if the browser uses the Blink rendering engine. This can be verified by navigating to chrome://gpu or looking for 'Blink' in the user agent stringAffected if The browser uses Blink (Google Chrome or Chromium-based browsers like Opera, Yandex, etc.)
-
Verify Web Audio API usageThis vulnerability affects the ReverbConvolverStage component of the Web Audio API. Check if any web pages or applications loaded in the browser use the Web Audio API, particularly AudioContext.createConvolver() methodAffected if The browser loads web content that processes audio through the Web Audio API convolver node, allowing specially crafted impulseResponse audio data to trigger the out-of-bounds read
A user is affected if they are running Google Chrome or a Chromium-based browser version 30.0.1599.65 or below, or any of the specifically listed 30.0.1599.x versions, and process audio content using the Web Audio API's convolver node.
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 dataUpdate Google Chrome to version 30.0.1599.66 or later, or update any Chromium-based browsers to versions containing the fix. No application-level remediation available as this is a browser engine vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2917 — 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-2917 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