dbcve.org
ChromeWeb browser · Google

CVE-2012-5108

HIGH · 9.3 CVSS v2.0 Published 2012-10-09
Fix available
A fix is available. Upgrade to after 22.0.1229.91 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Race condition in Google Chrome before 22.0.1229.92 allows remote attackers to execute arbitrary code via vectors related to audio devices.

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 confidence

A race condition vulnerability in Google Chrome versions prior to 22.0.1229.92 allows remote attackers to achieve arbitrary code execution through manipulation of audio device handling. The flaw exists in how the browser handles audio device interactions, where concurrent access patterns create a window for exploitation.

MitigationUpdate Google Chrome to version 22.0.1229.92 or later. In enterprise environments, deploy the updated browser version through endpoint management systems and verify complete coverage across the fleet.

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:<= 22.0.1229.91= 22.0.1229.0= 22.0.1229.1= 22.0.1229.2= 22.0.1229.3= 22.0.1229.4= 22.0.1229.6= 22.0.1229.7= 22.0.1229.8= 22.0.1229.9= 22.0.1229.10= 22.0.1229.11

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 Google Chrome is installed
    Check for the Chrome executable on the system. On Windows, look for chrome.exe in Program Files or Program Files (x86). On macOS, check /Applications/Google Chrome.app. On Linux, check common locations like /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or launch Chrome with the --version flag from command line. Note the full version number displayed (for example: 22.0.1229.91).
    Affected if A version number is returned that falls within or below the affected range
  3. Compare version against affected range
    Compare your installed version number to the list of affected versions: 22.0.1229.0 through 22.0.1229.91, including specific builds 22.0.1229.0 through 22.0.1229.11. If your version is 22.0.1229.92 or later, you are not affected.
    Affected if The installed version is 22.0.1229.91 or below, or matches any of the specific build numbers listed (22.0.1229.0 through 22.0.1229.11)
  4. Confirm audio device feature is in use
    The vulnerability exists in audio device handling. Check if Chrome's audio output is enabled by going to chrome://settings -> Show advanced settings -> Privacy section -> Content settings -> Media. Alternatively, verify if any audio playback has occurred in the browser.
    Affected if Audio handling is enabled and the browser has been used for audio playback, indicating the vulnerable code path could be reached

You are affected if Google Chrome version 22.0.1229.91 or below is installed and audio device handling is active on the system.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 22.0.1229.91
Interim mitigation

Update Google Chrome to version 22.0.1229.92 or later. In enterprise environments, deploy the updated browser version through endpoint management systems and verify complete coverage across the fleet.

Recommended fix High confidence

Chrome 22.0.1229.92 or later

  1. Open Google Chrome
  2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
  3. Click 'Check for updates' or the app will automatically check
  4. If an update is available, click 'Update Google Chrome'
  5. Restart the browser to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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