dbcve.org
ChromeWeb browser · Google

CVE-2013-2912

HIGH · 7.5 CVSS v2.0 Published 2013-10-02
Fix available
A fix is available. Upgrade to after 30.0.1599.65 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 the PepperInProcessRouter::SendToHost function in content/renderer/pepper/pepper_in_process_router.cc in the Pepper Plug-in API (PPAPI) in Google Chrome before 30.0.1599.66 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving a resource-destruction message.

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 the PepperInProcessRouter::SendToHost function within Chrome's PPAPI (Pepper Plug-in API). The flaw occurs when handling resource-destruction messages, where a memory object is freed but still referenced, leading to potential denial of service or unspecified code execution. Affects Chrome versions prior to 30.0.1599.66.

MitigationUpgrade Google Chrome to version 30.0.1599.66 or later. No code-level remediation required; this is a client-side browser update.

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:<= 30.0.1599.65= 30.0.1599.0= 30.0.1599.1= 30.0.1599.2= 30.0.1599.4= 30.0.1599.5= 30.0.1599.6= 30.0.1599.7= 30.0.1599.8= 30.0.1599.9= 30.0.1599.10= 30.0.1599.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
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. Verify Google Chrome is installed
    Open a terminal or command prompt and run: chrome --version (Linux/macOS) or chrome.exe --version (Windows). Alternatively, open Chrome and navigate to chrome://settings/help to view the version.
    Affected if Google Chrome is not installed - not affected. If installed, proceed to version check.
  2. Determine the installed Chrome version
    Run 'chrome --version' or 'chrome.exe --version' from command line, or check chrome://settings/help in the browser address bar. Note the full version number (e.g., 30.0.1599.65).
    Affected if Version cannot be determined - unable to assess. Continue if version is visible.
  3. Compare against affected version ranges
    Compare your installed version to: any version <= 30.0.1599.65, or exactly versions 30.0.1599.0 through 30.0.1599.11.
    Affected if If version matches <= 30.0.1599.65 OR equals 30.0.1599.0 through 30.0.1599.11, the environment falls within the affected range.
  4. Confirm PPAPI is enabled (required attack surface)
    PPAPI (Pepper Plug-in API) is typically enabled by default in affected Chrome versions. To verify, navigate to chrome://plugins and look for 'Pepper Flash' or similar PPAPI-based plugins listed.
    Affected if PPAPI is disabled or not present - the specific attack surface may not be available, though the vulnerable code still exists in the binary.

User is affected if Google Chrome version is 30.0.1599.65 or earlier, or any of the specific versions 30.0.1599.0 through 30.0.1599.11, regardless of PPAPI plugin status since the vulnerable code exists in the browser binary.

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

Upgrade Google Chrome to version 30.0.1599.66 or later. No code-level remediation required; this is a client-side browser update.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
2.5 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-2013-2912 — 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-2013-2912 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