CVE-2020-16045 in the critical feed json
Use after Free in Payments in Google Chrome on Android prior to 87.0.4280.66 allowed a remote attacker who had compromised the renderer pro…
published 5y ago modified 4mo ago also EUVD-2020-8012
- cvss
- 9.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Use after Free in Payments in Google Chrome on Android prior to 87.0.4280.66 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Patch / fix
- Google Chrome 87.0.4280.66
Is CVE-2020-16045 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.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
chromereleases.googleblog.com
/2020/11/stable-channel-update-for-desktop_17.html
release-notes, vendor-advisory
-
crbug.com
/1125614
permissions-required, vendor-advisory
Sources
- CVE List CVE-2020-16045
- NVD CVE-2020-16045
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.