CVE-2013-0910 json
Google Chrome before 25.0.1364.152 does not properly manage the interaction between the browser process and renderer processes during autho…
published 13y ago modified 4mo ago also EUVD-2013-0921
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Google Chrome before 25.0.1364.152 does not properly manage the interaction between the browser process and renderer processes during authorization of the loading of a plug-in, which makes it easier for remote attackers to bypass intended access restrictions via vectors involving a blocked plug-in.
Patch / fix
- google chrome 25.0.1364.152
Is CVE-2013-0910 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.34% chance of exploitation in the next 30 days, higher than 71% 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
- Weakness
-
- CWE-287 Improper Authentication
- Technology feeds
References
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A16574
vdb-entry, signature
- googlechromereleases.blogspot.com /2013/03/stable-channel-update_4.html
- src.chromium.org /viewvc/chrome?view=rev&revision=180103
- codereview.chromium.org /12086077
- code.google.com /p/chromium/issues/detail?id=172573
Sources
- CVE List CVE-2013-0910
- NVD CVE-2013-0910
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.