Linux · Ubuntu · Package update · January 2, 2023

chromium-codecs-ffmpeg-extra 89.0.4389.82-0ubuntu0.18.04.1: chromium-codecs-ffmpeg-extra 89.0.4389.82-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)

chromium-codecs-ffmpeg-extra 89.0.4389.82-0ubuntu0.18.04.1, released January 2, 2023, fixes 96 CVEs in chromium-codecs-ffmpeg-extra. 4 of them are being exploited (CVE-2021-21166); 4 on CISA KEV. Patch Radar priority: Patch now. The product is no longer supported.

Patch now4 on CISA KEVUnsupported product
CVEs closed
96
None rated Critical
Exploited
4
CVE-2021-21166
Highest CVSS
6.8
Base score, 0 to 10
Highest EPSS
0.9960
99th percentile

Priority of the 96 CVEs

Patch now 4 Urgent 0 High 0 Routine 92

Fixed package versions

ProductReleaseFixed in
chromium-codecs-ffmpeg-extraUbuntu 18.04.6 LTS (bionic)89.0.4389.82-0ubuntu0.18.04.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Patch now CVE-2021-21166 Chromium CVE-2021-21166: Object lifecycle issue in audion/a 0.2403 KEVExploited
Patch now CVE-2021-21148 Chromium CVE-2021-21148: Heap buffer overflow in V8n/a 0.1997 KEVExploited
Patch now CVE-2020-6572 chromium-browser: Use after free in Media in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to execute arbitrary code vi...n/a 0.1059 KEVExploited
Patch now CVE-2021-21193 Chromium CVE-2021-21193: Use after free in Blinkn/a 0.0995 KEVExploited
Routine CVE-2020-16040 chromium-browser: Insufficient data validation in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to potentially ex...n/a 0.9960 None reported
Routine CVE-2021-21132 Chromium CVE-2021-21132: Inappropriate implementation in DevToolsn/a 0.2511 None reported
Routine CVE-2021-21135 Chromium CVE-2021-21135: Inappropriate implementation in Performance APIn/a 0.2066 None reported
Routine CVE-2021-21118 Chromium: CVE-2021-21118 Insufficient data validation in V8n/a 0.1804 None reported
Routine CVE-2021-21177 Chromium CVE-2021-21177: Insufficient policy enforcement in Autofilln/a 0.1729 None reported
Routine CVE-2021-21123 Chromium CVE-2021-21123: Insufficient data validation in File System APIn/a 0.1091 None reported
Routine CVE-2021-21157 Chromium CVE-2021-21157: Use after free in Web Socketsn/a 0.0946 None reported
Routine CVE-2021-21126 Chromium CVE-2021-21126: Insufficient policy enforcement in extensionsn/a 0.0941 None reported
Routine CVE-2021-21125 Chromium CVE-2021-21125: Insufficient policy enforcement in File System APIn/a 0.0872 None reported
Routine CVE-2021-21124 Chromium CVE-2021-21124: Potential user after free in Speech Recognizern/a 0.0847 None reported
Routine CVE-2021-21131 Chromium CVE-2021-21131: Insufficient policy enforcement in File System APIn/a 0.0825 None reported
Routine CVE-2021-21122 Chromium CVE-2021-21122: Use after free in Blinkn/a 0.0756 None reported
Routine CVE-2021-21120 Chromium CVE-2021-21120: Use after free in WebSQLn/a 0.0742 None reported
Routine CVE-2021-21119 Chromium CVE-2021-21119: Use after free in Median/a 0.0736 None reported
Routine CVE-2021-21128 Chromium CVE-2021-21128: Heap buffer overflow in Blinkn/a 0.0702 None reported
Routine CVE-2021-21121 Chromium CVE-2021-21121: Use after free in Omniboxn/a 0.0668 None reported
Routine CVE-2021-21137 Chromium CVE-2021-21137: Inappropriate implementation in DevToolsn/a 0.0639 None reported
Routine CVE-2021-21127 Chromium CVE-2021-21127: Insufficient policy enforcement in extensionsn/a 0.0634 None reported
Routine CVE-2021-21129 Chromium CVE-2021-21129: Insufficient policy enforcement in File System APIn/a 0.0588 None reported
Routine CVE-2021-21130 Chromium CVE-2021-21130: Insufficient policy enforcement in File System APIn/a 0.0588 None reported
Routine CVE-2021-21141 Chromium CVE-2021-21141: Insufficient policy enforcement in File System API6.5 0.0587 None reported
Showing 1 to 25 of 96 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.