CVE-2013-0892 json
Multiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on…
published 2013-02-23 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-0903
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allow remote attackers to cause a denial of service or possibly have other impact via unknown vectors.
Patch / fix
- google chrome 25.0.1364.97, 25.0.1364.99
- 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.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
lists.opensuse.org
/opensuse-updates/2013-03/msg00045.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15586
vdb-entry, signature
- googlechromereleases.blogspot.com /2013/02/stable-channel-update_21.html
- code.google.com /p/chromium/issues/detail?id=166493
- code.google.com /p/chromium/issues/detail?id=164958
- code.google.com /p/chromium/issues/detail?id=165747
- code.google.com /p/chromium/issues/detail?id=164946
- code.google.com /p/chromium/issues/detail?id=165836
- code.google.com /p/chromium/issues/detail?id=168710
- code.google.com /p/chromium/issues/detail?id=169295
Sources
- CVE List CVE-2013-0892
- NVD CVE-2013-0892
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.