CVE-2009-2555 google
google: no CVSS score yet. EPSS 3.4% estimated probability of exploitation activity in the next 30 days.
On this page
Heap-based buffer overflow in src/jsregexp.cc in Google V8 before 1.1.10.14, as used in Google Chrome before 2.0.172.37, allows remote attackers to execute arbitrary code in the Chrome sandbox via a crafted JavaScript regular expression.
- EPSS
- 3.4% (unchanged from 3.4% a week ago; 3.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://code.google.com/p/chromium/issues/detail?id=14719
- Vendor advisory: http://googlechromereleases.blogspot.com/2009/07/stable-beta-update-bug-fixes.html
- Vendor advisory: http://secunia.com/advisories/35844
Ask an AI about this CVE
Show the prompt
Explain CVE-2009-2555 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2009-2555?via=ask-ai-copy and https://cve.bz/cve/CVE-2009-2555?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2009-2555 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| google:v8 | through 1.0 |
| google:chrome | through 2.0.172.33 |
| google:chrome | 0.2.149.29 |
| google:chrome | 0.2.149.30 |
| google:chrome | 0.2.152.1 |
| google:chrome | 0.2.153.1 |
| google:chrome | 0.3.154.0 |
| google:chrome | 0.3.154.3 |
| google:chrome | 0.4.154.18 |
| google:chrome | 0.4.154.22 |
| google:chrome | 0.4.154.31 |
| google:chrome | 0.4.154.33 |
| google:chrome | 1.0.154.36 |
| google:chrome | 1.0.154.39 |
| google:chrome | 1.0.154.42 |
| google:chrome | 1.0.154.43 |
| google:chrome | 1.0.154.46 |
| google:chrome | 1.0.154.48 |
| google:chrome | 1.0.154.52 |
| google:chrome | 1.0.154.53 |
| google:chrome | 1.0.154.59 |
| google:chrome | 2.0.156.1 |
| google:chrome | 2.0.157.0 |
| google:chrome | 2.0.157.2 |
| google:chrome | 2.0.158.0 |
| google:chrome | 2.0.159.0 |
| google:chrome | 2.0.172 |
| google:chrome | 2.0.172.30 |
| google:chrome | 2.0.172.31 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).
References
- http://code.google.com/p/chromium/issues/detail?id=14719
- http://googlechromereleases.blogspot.com/2009/07/stable-beta-update-bug-fixes.html
- http://secunia.com/advisories/35844
- http://www.vupen.com/english/advisories/2009/1924
- http://codereview.chromium.org/141042
- http://codereview.chromium.org/141042/diff/6/1004
- http://www.osvdb.org/55939
- http://www.securityfocus.com/bid/35722
- https://exchange.xforce.ibmcloud.com/vulnerabilities/51801