Linux ·
Ubuntu · Package update · January 3, 2020
Ubuntu · Package update · January 3, 2020chromium-browser 79.0.3945.79-0ubuntu0.18.04.1: chromium-browser 79.0.3945.79-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-browser 79.0.3945.79-0ubuntu0.18.04.1, released January 3, 2020, fixes 35 CVEs in chromium-browser. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.
HighUnsupported product
CVEs closed
35
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0643
93rd percentile
Priority of the 35 CVEs
Patch now 0
Urgent 0
High 1
Routine 34
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-browser | Ubuntu 18.04.6 LTS (bionic) | 79.0.3945.79-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2019-13734 | chromium-browser: Out of bounds write in SQLite in Google Chrome prior to 79.0.3945.79allowed a remote attacker to potentially exploit... | 8.8 | 0.0395 | None reported |
| Routine | CVE-2019-13764 | chromium-browser: Type confusion in JavaScript in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit... | n/a | 0.0643 | None reported |
| Routine | CVE-2019-13750 | chromium-browser: Insufficient data validation in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to bypass def... | 6.5 | 0.0241 | None reported |
| Routine | CVE-2019-13726 | chromium-browser: Buffer overflow in password manager in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to execute arbit... | n/a | 0.0219 | None reported |
| Routine | CVE-2019-13751 | libsqlite3-tcl: Uninitialized data in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain potentially s... | 6.5 | 0.0200 | None reported |
| Routine | CVE-2019-13725 | chromium-browser: Use-after-free in Bluetooth in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to execute arbitrary cod... | n/a | 0.0197 | None reported |
| Routine | CVE-2019-13730 | chromium-browser: Type confusion in JavaScript in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit... | n/a | 0.0195 | None reported |
| Routine | CVE-2019-13735 | chromium-browser: Out of bounds write in JavaScript in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to execute arbitra... | n/a | 0.0184 | None reported |
| Routine | CVE-2019-13752 | chromium-browser: Out of bounds read in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain potentially s... | 6.5 | 0.0171 | None reported |
| Routine | CVE-2019-13753 | chromium-browser: Out of bounds read in SQLite in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to obtain potentially s... | 6.5 | 0.0171 | None reported |
| Routine | CVE-2019-13728 | chromium-browser: Out of bounds write in JavaScript in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exp... | n/a | 0.0157 | None reported |
| Routine | CVE-2019-13736 | chromium-browser: Integer overflow in PDFium in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit he... | n/a | 0.0154 | None reported |
| Routine | CVE-2019-13745 | chromium-browser: Insufficient policy enforcement in audio in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to leak cro... | n/a | 0.0151 | None reported |
| Routine | CVE-2019-13729 | chromium-codecs-ffmpeg-extra: Use-after-free in WebSockets in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit... | n/a | 0.0146 | None reported |
| Routine | CVE-2019-13727 | chromium-browser: Insufficient policy enforcement in WebSockets in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to byp... | n/a | 0.0143 | None reported |
| Routine | CVE-2019-13744 | chromium-browser: Insufficient policy enforcement in cookies in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to leak c... | n/a | 0.0143 | None reported |
| Routine | CVE-2019-13737 | chromium-browser: Insufficient policy enforcement in autocomplete in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to o... | n/a | 0.0138 | None reported |
| Routine | CVE-2019-13746 | chromium-browser: Insufficient policy enforcement in Omnibox in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to spoof... | n/a | 0.0136 | None reported |
| Routine | CVE-2019-13732 | chromium-browser: Use-after-free in WebAudio in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to potentially exploit he... | n/a | 0.0134 | None reported |
| Routine | CVE-2019-13754 | chromium-codecs-ffmpeg: Insufficient policy enforcement in extensions in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to byp... | n/a | 0.0131 | None reported |
| Routine | CVE-2019-13738 | chromium-browser: Insufficient policy enforcement in navigation in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to byp... | n/a | 0.0131 | None reported |
| Routine | CVE-2019-13759 | chromium-browser: Incorrect security UI in interstitials in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to perform do... | n/a | 0.0129 | None reported |
| Routine | CVE-2019-13739 | chromium-chromedriver: Insufficient policy enforcement in Omnibox in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to perfor... | n/a | 0.0129 | None reported |
| Routine | CVE-2019-13756 | chromium-codecs-ffmpeg-extra: Incorrect security UI in printing in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to perform domain... | n/a | 0.0128 | None reported |
| Routine | CVE-2019-13743 | chromium-browser: Incorrect security UI in external protocol handling in Google Chrome prior to 79.0.3945.79 allowed a remote attacker... | n/a | 0.0128 | None reported |
Showing 1 to 25 of 35
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.