CVE-2012-5142 in the critical feed json
Google Chrome before 23.0.1271.97 does not properly handle history navigation, which allows remote attackers to execute arbitrary code or c…
published 2012-12-12 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5065
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Google Chrome before 23.0.1271.97 does not properly handle history navigation, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors.
Patch / fix
- chromium openSUSE Tumbleweed 55.0.2883.75-3.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
opensuse advisories openSUSE-SU-2024:10171-1openSUSE-SU-2024:12948-1
Exploit prediction
2.73% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
- Technology feeds
References
-
lists.opensuse.org
/opensuse-updates/2012-12/msg00073.html
vendor-advisory
- googlechromereleases.blogspot.com /2012/12/stable-channel-update.html
- code.google.com /p/chromium/issues/detail?id=160803
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A16173
vdb-entry, signature
Sources
- CVE List CVE-2012-5142
- NVD CVE-2012-5142
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.