dbcve.org
ChromeWeb browser · Google

CVE-2011-3882

HIGH · 7.5 CVSS v2.0 Published 2011-10-25
Fix available
A fix is available. Upgrade to 15.0.874.102 or later.
See remediation →
84/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
Use-after-free vulnerability in Google Chrome before 15.0.874.102 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to media buffers.

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

Use-after-free vulnerability in Google Chrome's media buffer handling allows remote attackers to access freed memory, potentially leading to denial of service or arbitrary code execution. The vulnerability exists in versions prior to 15.0.874.102 and is triggered through specially crafted media content.

MitigationUpgrade Google Chrome to version 15.0.874.102 or later. For enterprise environments, deploy the updated browser via standard software distribution mechanisms and verify compliance.

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

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

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

  1. Check installed Chrome version
    Open Google Chrome and navigate to chrome://version, or click Help > About Google Chrome. The version number is displayed at the top of the page.
    Affected if The displayed version number is less than 15.0.874.102 (for example, 15.0.874.101, 14.x.x.x, 13.x.x.x, etc.)
  2. Verify media feature is accessible
    Confirm that the browser can handle media content by attempting to load a media file or visiting a website with embedded audio/video. This vulnerability affects the media buffer handling subsystem.
    Affected if Media playback features are functional and the browser version is below 15.0.874.102
  3. Check Chrome channel and update status
    Navigate to chrome://settings/help to view the current version, update status, and channel (stable, beta, dev, Canary).
    Affected if The browser is on a channel or version that has not yet received the 15.0.874.102 security update.

You are affected if Google Chrome is installed with a version lower than 15.0.874.102 and the browser supports media content playback, which is the default configuration.

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

Upgrade Google Chrome to version 15.0.874.102 or later. For enterprise environments, deploy the updated browser via standard software distribution mechanisms and verify compliance.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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