dbcve.org
ChromeWeb browser · Google

CVE-2011-3080

HIGH · 7.6 CVSS v2.0 Published 2012-05-01
Fix available
A fix is available. Upgrade to 18.0.1025.168 or later.
See remediation →
85/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
Race condition in the Inter-process Communication (IPC) implementation in Google Chrome before 18.0.1025.168 allows attackers to bypass intended sandbox restrictions via unspecified 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 confidence

A race condition in Google Chrome's Inter-process Communication (IPC) implementation before version 18.0.1025.168 allowed attackers to bypass the browser's sandbox security restrictions through unspecified vectors exploiting timing windows in IPC handling.

MitigationUpdate Google Chrome to version 18.0.1025.168 or later to patch the sandbox bypass vulnerability.

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:< 18.0.1025.168

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

AV:N/AC:H/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. Determine installed Google Chrome version
    Navigate to Chrome menu > Help > About Google Chrome, or enter chrome://version in the address bar
    Affected if The displayed version number is less than 18.0.1025.168 (for example, 18.0.1025.151, 17.x, 16.x, etc.)
  2. Check Chrome version via command line
    On Windows, run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version' or check the executable properties. On macOS, run 'defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleVersion'. On Linux, run 'google-chrome --version' or check the package manager
    Affected if The version output is any version below 18.0.1025.168
  3. Verify if sandbox is enabled
    Navigate to chrome://sandbox/ in the browser and look for the 'Sandbox' status column, or check if the --no-sandbox flag is being used in any shortcuts or scripts launching Chrome
    Affected if Chrome is running with sandbox disabled (--no-sandbox flag present) AND the version is below 18.0.1025.168 - this combination makes exploitation more likely to succeed

If Google Chrome version is below 18.0.1025.168, the environment is vulnerable to this IPC race condition that can bypass sandbox restrictions.

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 18.0.1025.168 or later
Fixed in 18.0.1025.168
Interim mitigation

Update Google Chrome to version 18.0.1025.168 or later to patch the sandbox bypass vulnerability.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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