ChromeWeb browser · Google
CVE-2012-2859
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 · uneditedGoogle Chrome before 21.0.1180.57 on Linux does not properly handle tabs, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors.
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 confidenceGoogle Chrome before version 21.0.1180.57 on Linux contains a flaw in tab handling that allows remote attackers to execute arbitrary code or crash the application. The vulnerability is triggered via unspecified vectors targeting the Linux platform specifically.
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
<= 21.0.1180.56= 21.0.1180.0= 21.0.1180.1= 21.0.1180.2= 21.0.1180.31= 21.0.1180.32= 21.0.1180.33= 21.0.1180.34= 21.0.1180.35= 21.0.1180.36= 21.0.1180.37= 21.0.1180.38CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installed on LinuxRun 'google-chrome --version' or 'google-chrome-stable --version' in a terminal, or check via package manager with 'dpkg -l | grep google-chrome' or 'rpm -qa | grep google-chrome' depending on your distributionAffected if Google Chrome is not installed or the command returns no output
-
Obtain the exact installed version numberExecute 'google-chrome --version' to get the precise version string (for example: Google Chrome 21.0.1180.56)Affected if The version command fails or returns no version number
-
Compare installed version against affected rangeCompare the version number obtained (e.g., 21.0.1180.56) against the affected versions: any version <= 21.0.1180.56, or exactly 21.0.1180.0 through 21.0.1180.38Affected if The installed version is 21.0.1180.56 or lower, OR matches any of 21.0.1180.0 through 21.0.1180.38
-
Confirm the platform is LinuxThis vulnerability affects only Linux. Verify the operating system with 'uname -a' or 'cat /etc/os-release'Affected if The system is running Linux and the Chrome version falls within the affected range
A user is affected if Google Chrome version 21.0.1180.56 or any version from 21.0.1180.0 through 21.0.1180.38 is installed on a Linux system.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Google Chrome on Linux systems to version 21.0.1180.57 or later to remediate this vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2012-2859 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-2859 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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