Linux ·
Ubuntu · Package update · September 25, 2018
Ubuntu · Package update · September 25, 2018chromium-browser 64.0.3282.119-0ubuntu1: chromium-browser 64.0.3282.119-0ubuntu1 for Ubuntu 18.04.6 LTS (bionic)
chromium-browser 64.0.3282.119-0ubuntu1, released September 25, 2018, fixes 25 CVEs in chromium-browser. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.
RoutineUnsupported product
CVEs closed
25
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0215
82nd percentile
Priority of the 25 CVEs
Patch now 0
Urgent 0
High 0
Routine 25
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-browser | Ubuntu 18.04.6 LTS (bionic) | 64.0.3282.119-0ubuntu1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2018-6031 | chromium-browser: Use after free in PDFium in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially exploit hea... | n/a | 0.0215 | None reported |
| Routine | CVE-2018-6034 | chromium-browser: Insufficient data validation in WebGL in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to perform an... | n/a | 0.0191 | None reported |
| Routine | CVE-2018-6043 | chromium-browser: Insufficient data validation in External Protocol Handler in Google Chrome prior to 64.0.3282.119 allowed a remote at... | n/a | 0.0174 | None reported |
| Routine | CVE-2018-6036 | chromium-browser: Insufficient data validation in V8 in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially l... | n/a | 0.0162 | None reported |
| Routine | CVE-2018-6037 | chromium-browser: Inappropriate implementation in autofill in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to obtain... | n/a | 0.0160 | None reported |
| Routine | CVE-2018-6038 | chromium-browser: Heap buffer overflow in WebGL in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to perform an out of... | n/a | 0.0154 | None reported |
| Routine | CVE-2018-6045 | chromium-browser: Insufficient policy enforcement in DevTools in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to pote... | n/a | 0.0154 | None reported |
| Routine | CVE-2018-6035 | chromium-browser: Insufficient policy enforcement in DevTools in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to pote... | n/a | 0.0153 | None reported |
| Routine | CVE-2018-6033 | chromium-browser: Insufficient data validation in Downloads in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potent... | n/a | 0.0147 | None reported |
| Routine | CVE-2018-6047 | chromium-browser: Insufficient policy enforcement in WebGL in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potenti... | n/a | 0.0144 | None reported |
| Routine | CVE-2018-6054 | chromium-browser: Use after free in WebUI in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially exploit heap... | n/a | 0.0143 | None reported |
| Routine | CVE-2018-6049 | chromium-browser: Incorrect security UI in permissions prompt in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoo... | n/a | 0.0143 | None reported |
| Routine | CVE-2018-6032 | chromium-browser: Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potenti... | n/a | 0.0141 | None reported |
| Routine | CVE-2018-6040 | chromium-browser: Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potenti... | n/a | 0.0140 | None reported |
| Routine | CVE-2018-6052 | chromium-browser: Lack of support for a non standard no-referrer policy value in Blink in Google Chrome prior to 64.0.3282.119 allowed... | n/a | 0.0135 | None reported |
| Routine | CVE-2018-6050 | chromium-browser: Incorrect security UI in Omnibox in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoof the conte... | n/a | 0.0134 | None reported |
| Routine | CVE-2018-6041 | chromium-browser: Incorrect security UI in navigation in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoof the co... | n/a | 0.0133 | None reported |
| Routine | CVE-2018-6048 | chromium-browser: Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potenti... | n/a | 0.0127 | None reported |
| Routine | CVE-2018-6051 | chromium-browser: XSS Auditor in Google Chrome prior to 64.0.3282.119, did not ensure the reporting URL was in the same origin as the p... | n/a | 0.0127 | None reported |
| Routine | CVE-2018-6042 | chromium-browser: Incorrect security UI in Omnibox in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoof the conte... | n/a | 0.0123 | None reported |
| Routine | CVE-2018-6039 | chromium-browser: Insufficient data validation in DevTools in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potenti... | n/a | 0.0118 | None reported |
| Routine | CVE-2018-6046 | chromium-browser: Insufficient data validation in DevTools in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potenti... | n/a | 0.0118 | None reported |
| Routine | CVE-2018-6055 | chromium-browser: Insufficient policy enforcement in Catalog Service in Google Chrome prior to 64.0.3282.119 allowed a remote attacker... | n/a | 0.0114 | None reported |
| Routine | CVE-2018-6119 | chromium-browser: Incorrect security UI in Omnibox in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to spoof the conte... | n/a | 0.0090 | None reported |
| Routine | CVE-2018-6053 | chromium-browser: Inappropriate implementation in New Tab Page in Google Chrome prior to 64.0.3282.119 allowed a local attacker to view... | n/a | 0.0074 | None reported |
Showing 1 to 25 of 25
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.