dbcve.org
ChromeWeb browser · Google

CVE-2014-3174

MEDIUM · 5.0 CVSS v2.0 Published 2014-08-27
Fix available
A fix is available. Upgrade to after 37.0.2062.93 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
modules/webaudio/BiquadDSPKernel.cpp in the Web Audio API implementation in Blink, as used in Google Chrome before 37.0.2062.94, does not properly consider concurrent threads during attempts to update biquad filter coefficients, which allows remote attackers to cause a denial of service (read of uninitialized memory) via crafted API calls.

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 race condition in Blink's Web Audio API BiquadDSPKernel.cpp fails to properly synchronize concurrent threads updating biquad filter coefficients, allowing crafted API calls to read uninitialized memory and cause denial of service.

MitigationUpgrade Google Chrome to version 37.0.2062.94 or later to obtain the patched Blink engine.

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:<= 37.0.2062.93= 37.0.2062.0= 37.0.2062.1= 37.0.2062.2= 37.0.2062.3= 37.0.2062.4= 37.0.2062.5= 37.0.2062.6= 37.0.2062.7= 37.0.2062.8= 37.0.2062.9= 37.0.2062.10

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
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 checks

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

  1. Check Google Chrome version
    Open chrome://settings/help in the browser or run 'google-chrome --version' in a command terminal to determine the installed version
    Affected if Version is 37.0.2062.93 or earlier, or matches any version from 37.0.2062.0 through 37.0.2062.10 (specific affected builds)
  2. Verify Web Audio API usage
    Inspect any web applications or extensions loaded in the browser for use of AudioContext, BiquadFilterNode, or other Web Audio API interfaces
    Affected if Web Audio API is being actively used in the browser session while Chrome version is within the affected range
  3. Review crash logs for Web Audio symptoms
    Access chrome://crashes or examine system event logs for crashes mentioning BiquadDSPKernel.cpp or uninitialized memory read errors related to audio processing
    Affected if Crashes involving the biquad filter component occur on vulnerable Chrome versions

User is affected if running Chrome version 37.0.2062.93 or earlier or any version 37.0.2062.0-37.0.2062.10 while using Web Audio API features that interact with biquad filters

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 37.0.2062.93
Interim mitigation

Upgrade Google Chrome to version 37.0.2062.94 or later to obtain the patched Blink engine.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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