Linux ·
Ubuntu · Package update · November 2, 2020
Ubuntu · Package update · November 2, 2020chromium-codecs-ffmpeg 86.0.4240.75-0ubuntu0.18.04.1: chromium-codecs-ffmpeg 86.0.4240.75-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 86.0.4240.75-0ubuntu0.18.04.1, released November 2, 2020, fixes 27 CVEs in chromium-codecs-ffmpeg. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.
HighUnsupported product
CVEs closed
27
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0248
84th percentile
Priority of the 27 CVEs
Patch now 0
Urgent 0
High 1
Routine 26
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 86.0.4240.75-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2020-15969 | firefox: ELSA-2020-4317: firefox security update (IMPORTANT) | 8.8 | 0.0174 | None reported |
| Routine | CVE-2020-15972 | chromium-browser: Use after free in audio in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially exploit heap... | n/a | 0.0248 | None reported |
| Routine | CVE-2020-15985 | chromium-browser-l10n: Inappropriate implementation in Blink in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to spoof secur... | n/a | 0.0164 | None reported |
| Routine | CVE-2020-15979 | chromium-browser: Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially ex... | n/a | 0.0160 | None reported |
| Routine | CVE-2020-15968 | chromium-browser: Use after free in Blink in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially exploit heap... | n/a | 0.0154 | None reported |
| Routine | CVE-2020-6557 | chromium-browser: Inappropriate implementation in networking in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to perfor... | n/a | 0.0152 | None reported |
| Routine | CVE-2020-15978 | chromium-browser: Insufficient data validation in navigation in Google Chrome on Android prior to 86.0.4240.75 allowed a remote attacke... | n/a | 0.0151 | None reported |
| Routine | CVE-2020-15974 | chromium-browser: Integer overflow in Blink in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to bypass site isolation v... | n/a | 0.0149 | None reported |
| Routine | CVE-2020-15976 | chromium-browser: Use after free in WebXR in Google Chrome on Android prior to 86.0.4240.75 allowed a remote attacker to potentially ex... | n/a | 0.0149 | None reported |
| Routine | CVE-2020-15977 | chromium-browser: Insufficient data validation in dialogs in Google Chrome on OS X prior to 86.0.4240.75 allowed a remote attacker to o... | n/a | 0.0149 | None reported |
| Routine | CVE-2020-15991 | chromium-browser: Use after free in password manager in Google Chrome prior to 86.0.4240.75 allowed a remote attacker who had compromis... | n/a | 0.0145 | None reported |
| Routine | CVE-2020-15992 | chromium-browser: Insufficient policy enforcement in networking in Google Chrome prior to 86.0.4240.75 allowed a remote attacker who ha... | n/a | 0.0142 | None reported |
| Routine | CVE-2020-15990 | chromium-browser: Use after free in autofill in Google Chrome prior to 86.0.4240.75 allowed a remote attacker who had compromised the r... | n/a | 0.0140 | None reported |
| Routine | CVE-2020-15967 | chromium-browser: Use after free in payments in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially perform a... | n/a | 0.0139 | None reported |
| Routine | CVE-2020-15970 | chromium-browser: Use after free in NFC in Google Chrome prior to 86.0.4240.75 allowed a remote attacker who had compromised the render... | n/a | 0.0139 | None reported |
| Routine | CVE-2020-15971 | chromium-browser: Use after free in printing in Google Chrome prior to 86.0.4240.75 allowed a remote attacker who had compromised the r... | n/a | 0.0139 | None reported |
| Routine | CVE-2020-15981 | chromium-browser: Out of bounds read in audio in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to obtain potentially se... | n/a | 0.0139 | None reported |
| Routine | CVE-2020-15982 | chromium-browser: Inappropriate implementation in cache in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to obtain pote... | n/a | 0.0139 | None reported |
| Routine | CVE-2020-15975 | chromium-browser: Integer overflow in SwiftShader in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially explo... | n/a | 0.0138 | None reported |
| Routine | CVE-2020-15986 | chromium-browser: Integer overflow in media in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially exploit hea... | n/a | 0.0134 | None reported |
| Routine | CVE-2020-15984 | chromium-browser: Insufficient policy enforcement in Omnibox in Google Chrome on iOS prior to 86.0.4240.75 allowed a remote attacker to... | n/a | 0.0130 | None reported |
| Routine | CVE-2020-15988 | chromium-browser: Insufficient policy enforcement in downloads in Google Chrome on Windows prior to 86.0.4240.75 allowed a remote attac... | n/a | 0.0121 | None reported |
| Routine | CVE-2020-15989 | chromium-browser: Uninitialized data in PDFium in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to obtain potentially s... | n/a | 0.0113 | None reported |
| Routine | CVE-2020-15987 | chromium-browser: Use after free in WebRTC in Google Chrome prior to 86.0.4240.75 allowed a remote attacker to potentially exploit heap... | n/a | 0.0106 | None reported |
| Routine | CVE-2020-15973 | chromium-browser: Insufficient policy enforcement in extensions in Google Chrome prior to 86.0.4240.75 allowed an attacker who convince... | n/a | 0.0103 | None reported |
Showing 1 to 25 of 27
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.