dbcve.org
ChromeWeb browser · Google

CVE-2011-2789

MEDIUM · 6.8 CVSS v2.0 Published 2011-08-03
Fix available
A fix is available. Upgrade to 13.0.782.107 or later.
See remediation →
77/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 13.0.782.107 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to instantiation of the Pepper plug-in.

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

Use-after-free vulnerability in Google Chrome versions prior to 13.0.782.107 where memory is improperly managed during instantiation of the Pepper plug-in framework. This allows remote attackers to potentially execute arbitrary code or cause a denial of service by accessing freed memory objects.

MitigationUpgrade Google Chrome to version 13.0.782.107 or later. If immediate upgrade is not feasible, consider disabling the Pepper plug-in API or restricting browser access to untrusted content sources.

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

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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 Google Chrome version
    Navigate to chrome://version or go to Menu > Help > About Google Chrome to see the full version number
    Affected if version is earlier than 13.0.782.107 (e.g., 13.0.782.100, 12.x.x.x, etc.)
  2. Verify Pepper plug-in framework is active
    Navigate to chrome://plugins and look for entries under the Pepper category, or check for loaded Pepper-based plugins (e.g., Adobe Flash Player Pepper, PDF viewer)
    Affected if any Pepper-based plugins are enabled or loaded in the browser
  3. Confirm Chrome is the affected browser
    Ensure the browser being checked is Google Chrome and not Chromium or a Chrome-based alternative
    Affected if the browser is Google Chrome with a version below 13.0.782.107 AND Pepper plugins are in use

You are affected if you are running Google Chrome version lower than 13.0.782.107 and have Pepper-based plugins enabled or automatically loaded.

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

Upgrade Google Chrome to version 13.0.782.107 or later. If immediate upgrade is not feasible, consider disabling the Pepper plug-in API or restricting browser access to untrusted content sources.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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