Description
The regex implementation in Google V8, as used in Google Chrome before 19.0.1084.46, allows remote attackers to cause a denial of service (invalid write operation) or possibly have unspecified other impact via unknown vectors.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 18.04 LTS | libv8-3.14 | No fix yet | — |
| Ubuntu 16.04 LTS | libv8-3.14 | No fix yet | — |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | chromium | 55.0.2883.75-3.1 | openSUSE-SU-2024:12948-1, openSUSE-SU-2024:10171-1 |
Advisories 2
- openSUSE-SU-2024:10171-1 chromedriver-55.0.2883.75-3.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026
- openSUSE-SU-2024:12948-1 ungoogled-chromium-113.0.5672.92-1.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026
References
- GLSA-201205-03 vendor-advisory
- oval:org.mitre.oval:def:15610 vdb-entry signature
- openSUSE-SU-2012:0656 vendor-advisory
- 1027067 vdb-entry
- http://googlechromereleases.blogspot.com/2012/05/stable-channel-update.html
- 53540 vdb-entry
- chrome-v8regex-code-exec(75597) vdb-entry
- http://code.google.com/p/chromium/issues/detail?id=122337