dbcve.org
ChromeWeb browser · Google

CVE-2011-2862

HIGH · 7.5 CVSS v2.0 Published 2011-09-19
Fix available
A fix is available. Upgrade to 14.0.835.163 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 14.0.835.163, does not properly restrict access to built-in objects, which has unspecified impact and remote attack 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 · moderate confidence

This vulnerability exists in Google V8 JavaScript engine (used by Chrome) where built-in objects are not properly restricted, potentially allowing malicious JavaScript to access or manipulate objects that should be protected.

MitigationUpgrade Google Chrome to version 14.0.835.163 or later to obtain the patched V8 engine. Organizations should ensure browser update policies are enforced.

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:< 14.0.835.163

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 installed Google Chrome version
    Navigate to chrome://settings/help or look at About Chrome in the menu to see the current version number
    Affected if Version is earlier than 14.0.835.163
  2. Verify Chrome is not auto-updated
    Check if Chrome's auto-update feature is enabled by visiting chrome://chrome/ or inspecting group policy settings for browser update policies
    Affected if Auto-update is disabled and the installed version remains below 14.0.835.163
  3. Confirm JavaScript is enabled
    JavaScript is enabled by default in Chrome; no user action required - verify in Settings > Privacy and security > Site Settings that JavaScript is not globally blocked
    Affected if JavaScript is enabled (default state) - this is required for the V8 engine vulnerability to be exploitable

User is affected if Google Chrome version is below 14.0.835.163 and JavaScript execution is enabled in the browser, since the V8 engine flaw can be triggered by malicious web pages.

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

Upgrade Google Chrome to version 14.0.835.163 or later to obtain the patched V8 engine. Organizations should ensure browser update policies are enforced.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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