dbcve.org
ChromeWeb browser · Google

CVE-2013-2870

HIGH · 9.3 CVSS v2.0 Published 2013-07-10
Fix available
A fix is available. Upgrade to after 28.0.1500.70 or later.
See remediation →
100/100
Remediation priority · Urgent
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 28.0.1500.71 allows remote servers to execute arbitrary code via crafted response traffic after a URL request.

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 28.0.1500.71 allows malicious remote servers to execute arbitrary code on the client system by sending crafted response traffic following a URL request, potentially leading to complete system compromise.

MitigationUpdate Google Chrome to version 28.0.1500.71 or later to patch the vulnerability. For enterprise environments, deploy the updated browser version through standard software distribution channels and verify successful installation.

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.70= 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
Debian LinuxOperating system
Affected:= 7.0

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

AV:N/AC:M/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. Check if Google Chrome is installed
    On Windows, open Add/Remove Programs or check C:\Program Files\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, run dpkg -l | grep google-chrome or rpm -qa | grep google-chrome.
    Affected if Google Chrome browser is present on the system
  2. Determine the installed Chrome version
    Launch Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number is displayed on that page. Alternatively, run 'google-chrome --version' from command line on Linux or check the executable properties on Windows.
    Affected if A version number is found (any installation)
  3. Compare installed version against affected range
    Compare your version number to the affected versions: any version prior to 28.0.1500.71, or specifically versions 28.0.1500.0 through 28.0.1500.12. Note that version 28.0.1500.71 and later are NOT affected.
    Affected if Installed version is 28.0.1500.70 or lower, or matches any of 28.0.1500.0 through 28.0.1500.12
  4. For Debian Linux systems, verify browser package
    Run 'dpkg -l | grep -i chrome' or check if the google-chrome-stable package is installed. Debian 7.0 ships with affected Chrome versions.
    Affected if Google Chrome is installed on a Debian 7.0 system

A user is affected if Google Chrome version 28.0.1500.70 or any version from 28.0.1500.0 through 28.0.1500.12 is installed on their system.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 28.0.1500.70
Interim mitigation

Update Google Chrome to version 28.0.1500.71 or later to patch the vulnerability. For enterprise environments, deploy the updated browser version through standard software distribution channels and verify successful installation.

Recommended fix High confidence

Chrome 28.0.1500.71 or later

  1. Upgrade Google Chrome to version 28.0.1500.71 or later by downloading the latest version from the official Google Chrome website or using the built-in update mechanism
  2. Verify the installed Chrome version by navigating to chrome://settings/help to confirm the version is 28.0.1500.71 or higher
  3. If using Debian Linux 7.0, ensure the system security updates are applied: run 'apt-get update && apt-get upgrade' or check for chrome-browser security updates via the package manager

Generated from the published advisory — verify against the referenced sources before acting.

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