Linux ·
Ubuntu · Package update · May 20, 2020
Ubuntu · Package update · May 20, 2020chromium-browser-l10n 83.0.4103.61-0ubuntu0.18.04.1: chromium-browser-l10n 83.0.4103.61-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-browser-l10n 83.0.4103.61-0ubuntu0.18.04.1, released May 20, 2020, fixes 27 CVEs in chromium-browser-l10n. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.
RoutineUnsupported product
CVEs closed
27
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0641
93rd percentile
Priority of the 27 CVEs
Patch now 0
Urgent 0
High 0
Routine 27
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-browser-l10n | Ubuntu 18.04.6 LTS (bionic) | 83.0.4103.61-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2020-6468 | chromium-browser: Type confusion in V8 in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap cor... | n/a | 0.0641 | None reported |
| Routine | CVE-2020-6473 | chromium-browser: Insufficient policy enforcement in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to obtain p... | n/a | 0.0178 | None reported |
| Routine | CVE-2020-6485 | chromium-browser: Insufficient data validation in media router in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had... | n/a | 0.0172 | None reported |
| Routine | CVE-2020-6474 | chromium-browser: Use after free in Blink in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap... | n/a | 0.0171 | None reported |
| Routine | CVE-2020-6467 | chromium-browser: Use after free in WebRTC in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to potentially exploit heap... | n/a | 0.0167 | None reported |
| Routine | CVE-2020-6475 | chromium-browser: Incorrect implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof sec... | n/a | 0.0167 | None reported |
| Routine | CVE-2020-6483 | chromium-browser: Insufficient policy enforcement in payments in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypas... | n/a | 0.0167 | None reported |
| Routine | CVE-2020-6486 | chromium-browser: Insufficient policy enforcement in navigations in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to by... | n/a | 0.0166 | None reported |
| Routine | CVE-2020-6489 | chromium-browser: Inappropriate implementation in developer tools in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who... | n/a | 0.0163 | None reported |
| Routine | CVE-2020-6465 | chromium-browser: Use after free in reader mode in Google Chrome on Android prior to 83.0.4103.61 allowed a remote attacker who had com... | n/a | 0.0163 | None reported |
| Routine | CVE-2020-6466 | chromium-browser: Use after free in media in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had compromised the rend... | n/a | 0.0163 | None reported |
| Routine | CVE-2020-6478 | chromium-browser: Inappropriate implementation in full screen in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof... | n/a | 0.0161 | None reported |
| Routine | CVE-2020-6479 | chromium-browser: Inappropriate implementation in sharing in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to spoof sec... | n/a | 0.0161 | None reported |
| Routine | CVE-2020-6487 | chromium-browser: Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypa... | n/a | 0.0160 | None reported |
| Routine | CVE-2020-6488 | chromium-browser: Insufficient policy enforcement in downloads in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypa... | n/a | 0.0158 | None reported |
| Routine | CVE-2020-6481 | chromium-browser: Insufficient policy enforcement in URL formatting in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to... | n/a | 0.0154 | None reported |
| Routine | CVE-2020-6484 | chromium-browser: Insufficient data validation in ChromeDriver in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to bypa... | n/a | 0.0153 | None reported |
| Routine | CVE-2020-6491 | chromium-browser: Insufficient data validation in site information in Google Chrome prior to 83.0.4103.61 allowed a remote attacker to... | n/a | 0.0150 | None reported |
| Routine | CVE-2020-6472 | chromium-browser: Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who con... | n/a | 0.0147 | None reported |
| Routine | CVE-2020-6490 | chromium-browser: Insufficient data validation in loader in Google Chrome prior to 83.0.4103.61 allowed a remote attacker who had been... | n/a | 0.0146 | None reported |
| Routine | CVE-2020-6471 | chromium-browser: Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who con... | n/a | 0.0140 | None reported |
| Routine | CVE-2020-6476 | chromium-browser: Insufficient policy enforcement in tab strip in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced... | n/a | 0.0134 | None reported |
| Routine | CVE-2020-6482 | chromium-browser: Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who con... | n/a | 0.0134 | None reported |
| Routine | CVE-2020-6480 | chromium-browser: Insufficient policy enforcement in enterprise in Google Chrome prior to 83.0.4103.61 allowed a local attacker to bypa... | n/a | 0.0122 | None reported |
| Routine | CVE-2020-6469 | chromium-browser: Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who con... | n/a | 0.0119 | None reported |
Showing 1 to 25 of 27
1Next
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.