Linux ·
Ubuntu · Package update · November 25, 2019
Ubuntu · Package update · November 25, 2019chromium-codecs-ffmpeg 77.0.3865.90-0ubuntu0.18.04.1: chromium-codecs-ffmpeg 77.0.3865.90-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 77.0.3865.90-0ubuntu0.18.04.1, released November 25, 2019, fixes 43 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
43
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0144
73rd percentile
Priority of the 43 CVEs
Patch now 0
Urgent 0
High 0
Routine 43
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 77.0.3865.90-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2019-5870 | chromium-browser: Use after free in media in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to potentially perform a san... | n/a | 0.0144 | None reported |
| Routine | CVE-2019-5881 | chromium-browser: Out of bounds read in SwiftShader in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to obtain potentia... | n/a | 0.0104 | None reported |
| Routine | CVE-2019-5877 | chromium-browser: Out of bounds memory access in JavaScript in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to potenti... | n/a | 0.0101 | None reported |
| Routine | CVE-2019-13670 | chromium-browser: Insufficient data validation in JavaScript in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to potent... | n/a | 0.0093 | None reported |
| Routine | CVE-2019-13687 | chromium-browser: Use after free in Blink in Google Chrome prior to 77.0.3865.90 allowed a remote attacker to potentially exploit heap... | n/a | 0.0092 | None reported |
| Routine | CVE-2019-13688 | chromium-browser: Use after free in Blink in Google Chrome prior to 77.0.3865.90 allowed a remote attacker to potentially exploit heap... | n/a | 0.0092 | None reported |
| Routine | CVE-2019-5876 | chromium-browser: Use after free in media in Google Chrome on Android prior to 77.0.3865.75 allowed a remote attacker to potentially ex... | n/a | 0.0092 | None reported |
| Routine | CVE-2019-13685 | chromium-browser: Use after free in sharing view in Google Chrome prior to 77.0.3865.90 allowed a remote attacker to potentially exploi... | n/a | 0.0091 | None reported |
| Routine | CVE-2019-13686 | chromium-browser: Use after free in offline mode in Google Chrome prior to 77.0.3865.90 allowed a remote attacker to potentially exploi... | n/a | 0.0091 | None reported |
| Routine | CVE-2019-5874 | chromium-browser: Insufficient filtering in URI schemes in Google Chrome on Windows prior to 77.0.3865.75 allowed a remote attacker to... | n/a | 0.0091 | None reported |
| Routine | CVE-2019-5878 | chromium-browser: Use after free in V8 in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to potentially exploit heap cor... | n/a | 0.0088 | None reported |
| Routine | CVE-2019-13666 | chromium-browser: Information leak in storage in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to leak cross-origin dat... | n/a | 0.0088 | None reported |
| Routine | CVE-2019-13683 | chromium-browser: Insufficient policy enforcement in developer tools in Google Chrome prior to 77.0.3865.75 allowed a remote attacker t... | n/a | 0.0088 | None reported |
| Routine | CVE-2019-5880 | chromium-browser: Insufficient policy enforcement in Blink in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to leak cro... | n/a | 0.0088 | None reported |
| Routine | CVE-2019-13668 | chromium-browser: Insufficient policy enforcement in developer tools in Google Chrome prior to 77.0.3865.75 allowed a remote attacker t... | n/a | 0.0085 | None reported |
| Routine | CVE-2019-13677 | chromium-browser: Insufficient policy enforcement in site isolation in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to... | n/a | 0.0085 | None reported |
| Routine | CVE-2019-5871 | chromium-browser: Heap buffer overflow in Skia in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to potentially exploit... | n/a | 0.0084 | None reported |
| Routine | CVE-2019-5869 | chromium-browser: Use after free in Blink in Google Chrome prior to 76.0.3809.132 allowed a remote attacker to potentially exploit heap... | n/a | 0.0077 | None reported |
| Routine | CVE-2019-13660 | chromium-browser: UI spoofing in Chromium in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to spoof notifications via a... | n/a | 0.0075 | None reported |
| Routine | CVE-2019-13682 | chromium-browser: Insufficient policy enforcement in external protocol handling in Google Chrome prior to 77.0.3865.75 allowed a remote... | n/a | 0.0074 | None reported |
| Routine | CVE-2019-13673 | chromium-browser: Insufficient data validation in developer tools in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to l... | n/a | 0.0074 | None reported |
| Routine | CVE-2019-13662 | chromium-browser: Insufficient policy enforcement in navigations in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to by... | n/a | 0.0073 | None reported |
| Routine | CVE-2019-13678 | chromium-browser: Incorrect data validation in downloads in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to perform do... | n/a | 0.0073 | None reported |
| Routine | CVE-2019-13692 | chromium-browser: Insufficient policy enforcement in reader mode in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to by... | n/a | 0.0072 | None reported |
| Routine | CVE-2019-13665 | chromium-browser: Insufficient filtering in Blink in Google Chrome prior to 77.0.3865.75 allowed a remote attacker to bypass multiple f... | n/a | 0.0071 | None reported |
Showing 1 to 25 of 43
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.