dbcve.org
ChromeWeb browser · Google

CVE-2013-2882

HIGH · 7.5 CVSS v2.0 Published 2013-07-31
Fix available
A fix is available. Upgrade to 0.10.16 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
Google V8, as used in Google Chrome before 28.0.1500.95, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that leverage "type confusion."

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

Type confusion vulnerability in the Google V8 JavaScript engine affecting Chrome browsers before version 28.0.1500.95. Remote attackers can exploit this flaw via specially crafted JavaScript to cause denial of service or potentially execute arbitrary code.

MitigationUpdate Google Chrome to version 28.0.1500.95 or later to patch the V8 JavaScript engine 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:<= 28.0.1500.94= 28.0.1500.0= 28.0.1500.2= 28.0.1500.3= 28.0.1500.4= 28.0.1500.5= 28.0.1500.6= 28.0.1500.8= 28.0.1500.9= 28.0.1500.10= 28.0.1500.11= 28.0.1500.12
OpenstackApplication
Affected:= 3.0
Debian LinuxOperating system
Affected:= 7.0
Node.jsApplication
Affected:>= 0.10.0, < 0.10.16

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 Google Chrome version
    Open chrome://version in the browser address bar or run 'google-chrome --version' from command line
    Affected if Version is 28.0.1500.94 or lower, or exactly matches 28.0.1500.0 through 28.0.1500.12 (excluding 28.0.1500.95)
  2. Check Node.js version
    Run 'node --version' from command line
    Affected if Version is 0.10.0 or higher but below 0.10.16
  3. Check V8 JavaScript engine version in Node.js
    Run 'node -p process.versions.v8' to display the bundled V8 engine version
    Affected if V8 version falls within the vulnerable range associated with Node.js 0.10.0 to 0.10.15
  4. Verify V8 engine is exposed in any application
    Search for applications or services that embed the V8 JavaScript engine, then identify their version strings
    Affected if The application uses a V8 build matching the affected version numbers from the CVE

You are affected if Google Chrome is version 28.0.1500.94 or below (or specific 28.0.1500.x versions), or Node.js is version 0.10.0 through 0.10.15, with the vulnerable V8 engine included.

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

Update Google Chrome to version 28.0.1500.95 or later to patch the V8 JavaScript engine vulnerability.

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-2013-2882 — 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-2882 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