dbcve.org
ChromeWeb browser · Google

CVE-2013-2879

MEDIUM · 5.8 CVSS v2.0 Published 2013-07-10
Fix available
A fix is available. Upgrade to after 28.0.1500.70 or later.
See remediation →
67/100
Remediation priority · Elevated
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 Chrome before 28.0.1500.71 does not properly determine the circumstances in which a renderer process can be considered a trusted process for sign-in and subsequent sync operations, which makes it easier for remote attackers to conduct phishing attacks via a crafted web site.

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

Google Chrome before 28.0.1500.71 had a flaw in its process trust model where it improperly determined when a renderer process (the component that displays web content) could be considered trusted for sign-in and Google Sync operations. This allowed malicious websites to potentially bypass the security boundary and impersonate trusted processes, facilitating phishing attacks.

MitigationUpdate Google Chrome to version 28.0.1500.71 or later to obtain the patch. In enterprise environments, deploy the updated browser version via standard endpoint management tools 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
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

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. Determine installed Google Chrome version
    Open Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number will be displayed on that page.
    Affected if The displayed version is 28.0.1500.70 or lower, or matches any of these specific versions: 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, or 28.0.1500.12.
  2. Check Chrome version via command line (Windows)
    Open Command Prompt and run: chrome --version or look in C:\Program Files\Google\Chrome\Application\ for the chrome.exe file and check its properties.
    Affected if The version shown is any of the affected versions listed above.
  3. Check Chrome version via command line (Linux/Debian)
    Run 'google-chrome --version' or 'chromium --version' in a terminal. For Debian 7.0, check with: dpkg -l | grep chromium or apt-cache policy chromium.
    Affected if The installed version matches any affected Chrome version, or for Debian systems the chromium package version is 28.0.1500.70 or lower.
  4. Verify patch status
    If the version is 28.0.1500.71 or higher, the vulnerability has been patched. The fix is included in version 28.0.1500.71 and all subsequent releases.
    Affected if The installed version is below 28.0.1500.71, meaning the process trust model vulnerability remains unpatched.

You are affected if Google Chrome version is 28.0.1500.70 or lower, or exactly matches any of the specific affected versions from 28.0.1500.0 through 28.0.1500.12.

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

Update Google Chrome to version 28.0.1500.71 or later to obtain the patch. In enterprise environments, deploy the updated browser version via standard endpoint management tools and verify successful installation.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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