Linux ·
Ubuntu · Package update · January 8, 2021
Ubuntu · Package update · January 8, 2021chromium-browser 86.0.4240.198-0ubuntu0.18.04.1: chromium-browser 86.0.4240.198-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-browser 86.0.4240.198-0ubuntu0.18.04.1, released January 8, 2021, fixes 15 CVEs in chromium-browser. 4 of them are being exploited (CVE-2020-15999); 4 on CISA KEV. Patch Radar priority: Patch now. The product is no longer supported.
Patch now4 on CISA KEVUnsupported product
CVEs closed
15
None rated Critical
Exploited
4
CVE-2020-15999
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.6389
99th percentile
Priority of the 15 CVEs
Patch now 4
Urgent 0
High 0
Routine 11
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-browser | Ubuntu 18.04.6 LTS (bionic) | 86.0.4240.198-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Patch now | CVE-2020-15999 | freetype2-demos: Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111allowed a remote attacker to potentially expl... | 8.6 | 0.6389 | KEVExploited |
| Patch now | CVE-2020-16009 | Google Chromium V8 Type Confusion Vulnerability | 8.8 | 0.4829 | KEVExploited |
| Patch now | CVE-2020-16013 | chromium-browser: Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.198 allowed a remote attacker to potentially e... | n/a | 0.0276 | KEVExploited |
| Patch now | CVE-2020-16017 | chromium-browser: Use after free in site isolation in Google Chrome prior to 86.0.4240.198 allowed a remote attacker who had compromise... | n/a | 0.0273 | KEVExploited |
| Routine | CVE-2020-16011 | chromium-browser: Heap buffer overflow in UI in Google Chrome on Windows prior to 86.0.4240.183 allowed a remote attacker who had compr... | n/a | 0.0241 | None reported |
| Routine | CVE-2020-16005 | chromium-browser: Insufficient policy enforcement in ANGLE in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potenti... | n/a | 0.0167 | None reported |
| Routine | CVE-2020-16006 | chromium-browser: Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially e... | n/a | 0.0167 | None reported |
| Routine | CVE-2020-16002 | chromium-browser: Use after free in PDFium in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit hea... | n/a | 0.0166 | None reported |
| Routine | CVE-2020-16000 | chromium-browser: Inappropriate implementation in Blink in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentiall... | n/a | 0.0160 | None reported |
| Routine | CVE-2020-16001 | chromium-browser: Use after free in media in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap... | n/a | 0.0159 | None reported |
| Routine | CVE-2020-16004 | chromium-browser: Use after free in user interface in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially exp... | n/a | 0.0152 | None reported |
| Routine | CVE-2020-16003 | chromium-browser: Use after free in printing in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit h... | n/a | 0.0149 | None reported |
| Routine | CVE-2020-16008 | chromium-browser: Stack buffer overflow in WebRTC in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially expl... | n/a | 0.0115 | None reported |
| Routine | CVE-2020-16016 | chromium-browser: Inappropriate implementation in base in Google Chrome prior to 86.0.4240.193 allowed a remote attacker who had compro... | n/a | 0.0087 | None reported |
| Routine | CVE-2020-16007 | chromium-browser: Insufficient data validation in installer in Google Chrome prior to 86.0.4240.183 allowed a local attacker to potenti... | n/a | 0.0027 | None reported |
Showing 1 to 15 of 15
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.