Linux ·
Ubuntu · Package update · November 2, 2021
Ubuntu · Package update · November 2, 2021chromium-codecs-ffmpeg 84.0.4147.105-0ubuntu0.18.04.1: chromium-codecs-ffmpeg 84.0.4147.105-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 84.0.4147.105-0ubuntu0.18.04.1, released November 2, 2021, fixes 39 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
39
None rated Critical
Exploited
0
None reported
Highest CVSS
6.5
Base score, 0 to 10
Highest EPSS
0.2161
97th percentile
Priority of the 39 CVEs
Patch now 0
Urgent 0
High 0
Routine 39
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 84.0.4147.105-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2020-6541 | chromium-browser: Use after free in WebUSB in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to potentially exploit hea... | n/a | 0.2161 | None reported |
| Routine | CVE-2020-6507 | chromium-browser: Out of bounds write in V8 in Google Chrome prior to 83.0.4103.106 allowed a remote attacker to potentially exploit he... | n/a | 0.1908 | None reported |
| Routine | CVE-2020-6519 | chromium-browser: Policy bypass in CSP in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to bypass content security poli... | n/a | 0.1027 | None reported |
| Routine | CVE-2020-6514 | chromium-browser-l10n: Inappropriate implementation in WebRTC in Google Chrome prior to 84.0.4147.89 allowed an attacker in a privileged net... | 6.5 | 0.0779 | None reported |
| Routine | CVE-2020-6516 | chromium-browser: Policy bypass in CORS in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to leak cross-origin data via... | n/a | 0.0477 | None reported |
| Routine | CVE-2020-6506 | chromium-browser: Insufficient policy enforcement in WebView in Google Chrome on Android prior to 83.0.4103.106 allowed a remote attack... | n/a | 0.0372 | None reported |
| Routine | CVE-2020-6513 | chromium-browser: Heap buffer overflow in PDFium in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploi... | n/a | 0.0297 | None reported |
| Routine | CVE-2020-6512 | chromium-browser: Type Confusion in V8 in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap cor... | n/a | 0.0295 | None reported |
| Routine | CVE-2020-6524 | chromium-browser: Heap buffer overflow in WebAudio in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially expl... | n/a | 0.0288 | None reported |
| Routine | CVE-2020-6517 | chromium-browser: Heap buffer overflow in history in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially explo... | n/a | 0.0279 | None reported |
| Routine | CVE-2020-6523 | chromium-browser: Out of bounds write in Skia in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit h... | n/a | 0.0272 | None reported |
| Routine | CVE-2020-6520 | chromium-browser: Buffer overflow in Skia in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap... | n/a | 0.0270 | None reported |
| Routine | CVE-2020-6518 | chromium-browser: Use after free in developer tools in Google Chrome prior to 84.0.4147.89 allowed a remote attacker who had convinced... | n/a | 0.0255 | None reported |
| Routine | CVE-2020-6515 | chromium-browser: Use after free in tab strip in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit h... | n/a | 0.0251 | None reported |
| Routine | CVE-2020-6533 | chromium-browser: Type Confusion in V8 in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap cor... | n/a | 0.0224 | None reported |
| Routine | CVE-2020-6534 | chromium-browser: Heap buffer overflow in WebRTC in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploi... | n/a | 0.0191 | None reported |
| Routine | CVE-2020-6525 | chromium-browser: Heap buffer overflow in Skia in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit... | n/a | 0.0186 | None reported |
| Routine | CVE-2020-6493 | chromium-browser: Use after free in WebAuthentication in Google Chrome prior to 83.0.4103.97 allowed a remote attacker who had compromi... | n/a | 0.0172 | None reported |
| Routine | CVE-2020-6526 | chromium-browser: Inappropriate implementation in iframe sandbox in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to by... | n/a | 0.0171 | None reported |
| Routine | CVE-2020-6521 | chromium-browser: Side-channel information leakage in autofill in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to obta... | n/a | 0.0170 | None reported |
| Routine | CVE-2020-6511 | chromium-codecs-ffmpeg-extra: Information leak in content security policy in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to leak... | n/a | 0.0169 | None reported |
| Routine | CVE-2020-6522 | chromium-browser: Inappropriate implementation in external protocol handlers in Google Chrome prior to 84.0.4147.89 allowed a remote at... | n/a | 0.0163 | None reported |
| Routine | CVE-2020-6510 | chromium-browser: Heap buffer overflow in background fetch in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentia... | n/a | 0.0158 | None reported |
| Routine | CVE-2020-6531 | chromium-browser: Side-channel information leakage in scroll to text in Google Chrome prior to 84.0.4147.89 allowed a remote attacker t... | n/a | 0.0157 | None reported |
| Routine | CVE-2020-6537 | chromium-browser: Type confusion in V8 in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to execute arbitrary code insi... | n/a | 0.0155 | None reported |
Showing 1 to 25 of 39
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.