dbcve.org
ChromeWeb browser · Google

CVE-2009-2935

HIGH · 10.0 CVSS v2.0 Published 2009-08-27
Fix available
A fix is available. Upgrade to after 2.0.172.37 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
Google V8, as used in Google Chrome before 2.0.172.43, allows remote attackers to bypass intended restrictions on reading memory, and possibly obtain sensitive information or execute arbitrary code in the Chrome sandbox, via crafted JavaScript.

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

A vulnerability in the Google V8 JavaScript engine (used in Chrome prior to 2.0.172.43) allows remote attackers to bypass sandbox restrictions and read memory beyond intended boundaries. This memory disclosure can potentially expose sensitive data or be chained with other exploits to achieve arbitrary code execution within the Chrome sandbox context.

MitigationUpdate Google Chrome to version 2.0.172.43 or later to remediate this vulnerability. Organizations should ensure automated browser update mechanisms are enabled and verify compliance across managed endpoints.

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:<= 2.0.172.37= 0.2.149.27= 0.2.149.29= 0.2.149.30= 0.2.152.1= 0.2.153.1= 0.3.154.0= 0.3.154.3= 0.4.154.18= 0.4.154.22= 0.4.154.31= 0.4.154.33

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

AV:N/AC:L/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. Determine installed Chrome version
    Open chrome://version in the browser address bar and note the version number displayed (the first line shows the Chrome version)
    Affected if The version is 2.0.172.37 or lower, or matches any of these specific versions: 0.2.149.27, 0.2.149.29, 0.2.149.30, 0.2.152.1, 0.2.153.1, 0.3.154.0, 0.3.154.3, 0.4.154.18, 0.4.154.22, 0.4.154.31, or 0.4.154.33
  2. Check Chrome channel and update status
    Navigate to chrome://settings/help to see the current version and whether automatic updates are enabled
    Affected if The browser shows a version below 2.0.172.43 and automatic updates appear disabled or outdated
  3. Verify V8 engine presence (confirming the vulnerable component exists)
    This vulnerability is in the V8 JavaScript engine bundled with Chrome. On Windows, V8 is embedded in chrome.dll; on Mac/Linux, check the Chrome version as the V8 version matches the Chrome release
    Affected if The browser is any affected Chrome version listed above - V8 is present by default in all standard Chrome installations

You are affected if your installed Chrome version is 2.0.172.37 or any earlier version, or matches one of the specific affected version numbers (0.2.149.x through 0.4.154.x series); versions 2.0.172.43 and later are not affected.

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

Update Google Chrome to version 2.0.172.43 or later to remediate this vulnerability. Organizations should ensure automated browser update mechanisms are enabled and verify compliance across managed endpoints.

Recommended fix High confidence

Google Chrome 2.0.172.43 or later (or current stable release)

  1. 1. Navigate to the official Google Chrome download page at google.com/chrome
  2. 2. Download and install the latest stable version of Google Chrome
  3. 3. If automated updates are enabled, Chrome will automatically update to the fixed version
Caveat Very old - modern Chrome versions have significantly different UI and features; ensure compatibility with any legacy systems or extensions

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

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-2009-2935 — 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-2009-2935 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