Linux ·
Ubuntu · Package update · November 25, 2019
Ubuntu · Package update · November 25, 2019chromium-codecs-ffmpeg 76.0.3809.87-0ubuntu0.18.04.1: chromium-codecs-ffmpeg 76.0.3809.87-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 76.0.3809.87-0ubuntu0.18.04.1, released November 25, 2019, fixes 15 CVEs in chromium-codecs-ffmpeg. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.
RoutineUnsupported product
CVEs closed
15
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0108
65th percentile
Priority of the 15 CVEs
Patch now 0
Urgent 0
High 0
Routine 15
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 76.0.3809.87-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2019-5852 | chromium-browser: Inappropriate implementation in JavaScript in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to obtain... | n/a | 0.0108 | None reported |
| Routine | CVE-2019-5850 | chromium-browser: Use after free in offline mode in Google Chrome prior to 76.0.3809.87 allowed a remote attacker who had compromised t... | n/a | 0.0101 | None reported |
| Routine | CVE-2019-5853 | chromium-browser: Inappropriate implementation in JavaScript in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to potent... | n/a | 0.0099 | None reported |
| Routine | CVE-2019-5858 | chromium-browser: Incorrect security UI in MacOS services integration in Google Chrome on OS X prior to 76.0.3809.87 allowed a local at... | n/a | 0.0094 | None reported |
| Routine | CVE-2019-5851 | chromium-browser: Use after free in WebAudio in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to potentially exploit he... | n/a | 0.0094 | None reported |
| Routine | CVE-2019-5859 | chromium-browser: Insufficient filtering in URI schemes in Google Chrome on Windows prior to 76.0.3809.87 allowed a remote attacker to... | n/a | 0.0092 | None reported |
| Routine | CVE-2019-5854 | chromium-browser: Integer overflow in PDFium in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to potentially exploit he... | n/a | 0.0091 | None reported |
| Routine | CVE-2019-5856 | chromium-browser: Insufficient policy enforcement in storage in Google Chrome prior to 76.0.3809.87 allowed a remote attacker who had c... | n/a | 0.0080 | None reported |
| Routine | CVE-2019-5862 | chromium-browser: Insufficient data validation in AppCache in Google Chrome prior to 76.0.3809.87 allowed a remote attacker who had com... | n/a | 0.0074 | None reported |
| Routine | CVE-2019-5865 | chromium-browser: Insufficient policy enforcement in navigations in Google Chrome prior to 76.0.3809.87 allowed a remote attacker who h... | n/a | 0.0074 | None reported |
| Routine | CVE-2019-5855 | chromium-browser: Integer overflow in PDFium in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to potentially exploit he... | n/a | 0.0072 | None reported |
| Routine | CVE-2019-5857 | chromium-browser: Inappropriate implementation in JavaScript in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to potent... | n/a | 0.0068 | None reported |
| Routine | CVE-2019-5861 | chromium-browser: Insufficient data validation in Blink in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to bypass anti... | n/a | 0.0064 | None reported |
| Routine | CVE-2019-5860 | chromium-browser: Use after free in PDFium in Google Chrome prior to 76.0.3809.87 allowed a remote attacker to potentially exploit heap... | n/a | 0.0059 | None reported |
| Routine | CVE-2019-5864 | chromium-browser: Insufficient data validation in CORS in Google Chrome prior to 76.0.3809.87 allowed an attacker who convinced a user... | n/a | 0.0046 | 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.