Linux ·
Ubuntu · Package update · June 3, 2020
Ubuntu · Package update · June 3, 2020chromium-browser-l10n 80.0.3987.87-0ubuntu0.18.04.1: chromium-browser-l10n 80.0.3987.87-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-browser-l10n 80.0.3987.87-0ubuntu0.18.04.1, released June 3, 2020, fixes 37 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
37
None rated Critical
Exploited
0
None reported
Highest CVSS
6.5
Base score, 0 to 10
Highest EPSS
0.0308
87th percentile
Priority of the 37 CVEs
Patch now 0
Urgent 0
High 0
Routine 37
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-browser-l10n | Ubuntu 18.04.6 LTS (bionic) | 80.0.3987.87-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2020-6390 | chromium-browser: Out of bounds memory access in streams in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentiall... | n/a | 0.0308 | None reported |
| Routine | CVE-2020-6402 | chromium-browser: Insufficient policy enforcement in downloads in Google Chrome on OS X prior to 80.0.3987.87 allowed an attacker who c... | n/a | 0.0266 | None reported |
| Routine | CVE-2020-6405 | lemon: Fixed (#1804823) | 6.5 | 0.0263 | None reported |
| Routine | CVE-2020-6385 | chromium-browser: Insufficient policy enforcement in storage in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass... | n/a | 0.0226 | None reported |
| Routine | CVE-2020-6382 | chromium-browser: Type confusion in JavaScript in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit... | n/a | 0.0226 | None reported |
| Routine | CVE-2020-6381 | chromium-browser: Integer overflow in JavaScript in Google Chrome on ChromeOS and Android prior to 80.0.3987.87 allowed a remote attack... | n/a | 0.0221 | None reported |
| Routine | CVE-2020-6404 | chromium-browser: Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially... | n/a | 0.0205 | None reported |
| Routine | CVE-2020-6388 | chromium-browser: Out of bounds access in WebAudio in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially expl... | n/a | 0.0204 | None reported |
| Routine | CVE-2020-6400 | chromium-browser: Inappropriate implementation in CORS in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cross-o... | n/a | 0.0200 | None reported |
| Routine | CVE-2020-6415 | chromium-browser: Inappropriate implementation in JavaScript in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potent... | n/a | 0.0199 | None reported |
| Routine | CVE-2020-6416 | chromium-browser: Insufficient data validation in streams in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potential... | n/a | 0.0199 | None reported |
| Routine | CVE-2020-6399 | chromium-browser: Insufficient policy enforcement in AppCache in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak... | n/a | 0.0199 | None reported |
| Routine | CVE-2020-6395 | chromium-browser: Out of bounds read in JavaScript in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to obtain potential... | n/a | 0.0198 | None reported |
| Routine | CVE-2020-6401 | chromium-browser: Insufficient validation of untrusted input in Omnibox in Google Chrome prior to 80.0.3987.87 allowed a remote attacke... | n/a | 0.0195 | None reported |
| Routine | CVE-2020-6397 | chromium-browser: Inappropriate implementation in sharing in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to spoof sec... | n/a | 0.0192 | None reported |
| Routine | CVE-2020-6413 | chromium-browser: Inappropriate implementation in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to bypass HTML... | n/a | 0.0191 | None reported |
| Routine | CVE-2020-6414 | chromium-browser: Insufficient policy enforcement in Safe Browsing in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to... | n/a | 0.0186 | None reported |
| Routine | CVE-2020-6393 | chromium-browser: Insufficient policy enforcement in Blink in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to leak cro... | n/a | 0.0185 | None reported |
| Routine | CVE-2020-6406 | chromium-browser: Use after free in audio in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit heap... | n/a | 0.0185 | None reported |
| Routine | CVE-2020-6387 | chromium-browser: Out of bounds write in WebRTC in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit... | n/a | 0.0181 | None reported |
| Routine | CVE-2020-6398 | chromium-browser: Use of uninitialized data in PDFium in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially e... | n/a | 0.0179 | None reported |
| Routine | CVE-2020-6389 | chromium-browser: Out of bounds write in WebRTC in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to potentially exploit... | n/a | 0.0174 | None reported |
| Routine | CVE-2020-6409 | chromium-browser: Inappropriate implementation in Omnibox in Google Chrome prior to 80.0.3987.87 allowed a remote attacker who convince... | n/a | 0.0174 | None reported |
| Routine | CVE-2020-6396 | chromium-browser: Inappropriate implementation in Skia in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to spoof the co... | n/a | 0.0174 | None reported |
| Routine | CVE-2020-6410 | chromium-browser: Insufficient policy enforcement in navigation in Google Chrome prior to 80.0.3987.87 allowed a remote attacker to con... | n/a | 0.0170 | None reported |
Showing 1 to 25 of 37
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.