CVE-2009-2555
Summary
| CVE | CVE-2009-2555 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2009-07-21 16:30:00 UTC |
| Updated | 2026-04-23 00:35:47 UTC |
| Description | 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. |
Risk And Classification
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
NoneConfidentiality
CompleteIntegrity
CompleteAvailability
CompleteAV:N/AC:M/Au:N/C:C/I:C/A:C
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Chrome | 0.2.149.29 | All | All | All | |
| Application | Chrome | 0.2.149.30 | All | All | All | |
| Application | Chrome | 0.2.152.1 | All | All | All | |
| Application | Chrome | 0.2.153.1 | All | All | All | |
| Application | Chrome | 0.3.154.0 | All | All | All | |
| Application | Chrome | 0.3.154.3 | All | All | All | |
| Application | Chrome | 0.4.154.18 | All | All | All | |
| Application | Chrome | 0.4.154.22 | All | All | All | |
| Application | Chrome | 0.4.154.31 | All | All | All | |
| Application | Chrome | 0.4.154.33 | All | All | All | |
| Application | Chrome | 1.0.154.36 | All | All | All | |
| Application | Chrome | 1.0.154.39 | All | All | All | |
| Application | Chrome | 1.0.154.42 | All | All | All | |
| Application | Chrome | 1.0.154.43 | All | All | All | |
| Application | Chrome | 1.0.154.46 | All | All | All | |
| Application | Chrome | 1.0.154.48 | All | All | All | |
| Application | Chrome | 1.0.154.52 | All | All | All | |
| Application | Chrome | 1.0.154.53 | All | All | All | |
| Application | Chrome | 1.0.154.59 | All | All | All | |
| Application | Chrome | 2.0.156.1 | All | All | All | |
| Application | Chrome | 2.0.157.0 | All | All | All | |
| Application | Chrome | 2.0.157.2 | All | All | All | |
| Application | Chrome | 2.0.158.0 | All | All | All | |
| Application | Chrome | 2.0.159.0 | All | All | All | |
| Application | Chrome | 2.0.172 | All | All | All | |
| Application | Chrome | 2.0.172.30 | All | All | All | |
| Application | Chrome | 2.0.172.31 | All | All | All | |
| Application | Chrome | All | All | All | All | |
| Application | V8 | All | All | All | All |
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Google Chrome JavaScript Regular Expression Handling Remote Code Execution Vulnerability | af854a3a-2127-422b-91ae-364da2661108 | www.securityfocus.com | |
| Google Chrome JavaScript Regular Expressions Memory Corruption - Secunia Advisories - Vulnerability Information - Secunia.com | af854a3a-2127-422b-91ae-364da2661108 | secunia.com | Vendor Advisory |
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | |
| Webmail : Solution de messagerie professionnelle - OVHcloud- OVH | af854a3a-2127-422b-91ae-364da2661108 | www.vupen.com | Vendor Advisory |
| src/jsregexp.cc - Issue 141042: Fix regexp bug reported on iit.edu. - Code Review | af854a3a-2127-422b-91ae-364da2661108 | codereview.chromium.org | |
| Issue 141042: Fix regexp bug reported on iit.edu. - Code Review | af854a3a-2127-422b-91ae-364da2661108 | codereview.chromium.org | |
| Issue 14719 - chromium - Security: possible memory corruption in v8 regex execution engine - Project Hosting on Google Code | af854a3a-2127-422b-91ae-364da2661108 | code.google.com | Vendor Advisory |
| www.osvdb.org/55939 | af854a3a-2127-422b-91ae-364da2661108 | www.osvdb.org | |
| Google Chrome Releases: Stable, Beta update: Bug fixes | af854a3a-2127-422b-91ae-364da2661108 | googlechromereleases.blogspot.com | Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.