Linux · Ubuntu · Package update · January 2, 2023

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

chromium-codecs-ffmpeg 100.0.4896.127-0ubuntu0.18.04.1, released January 2, 2023, fixes 34 CVEs in chromium-codecs-ffmpeg. One of them is being exploited (CVE-2022-1364); 1 on CISA KEV. Patch Radar priority: Patch now. The product is no longer supported.

Patch now1 on CISA KEVUnsupported product
CVEs closed
34
2 rated Critical
Exploited
1
CVE-2022-1364
Highest CVSS
9.6
Base score, 0 to 10
Highest EPSS
0.1706
97th percentile

Priority of the 34 CVEs

Patch now 1 Urgent 2 High 21 Routine 10

Fixed package versions

ProductReleaseFixed in
chromium-codecs-ffmpegUbuntu 18.04.6 LTS (bionic)100.0.4896.127-0ubuntu0.18.04.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Patch now CVE-2022-1364 Chromium: CVE-2022-1364: Type Confusion in V88.8 0.1392 KEVExploited
Urgent CVE-2022-1309 Chromium: CVE-2022-1309 Insufficient policy enforcement in developer tools9.6 0.0089 None reported
Urgent CVE-2022-1312 Chromium: CVE-2022-1312 Use after free in storage9.6 0.0064 None reported
High CVE-2022-1232 Chromium: CVE-2022-1232 Type Confusion in V88.8 0.1706 None reported
High CVE-2022-1134 Chromium: CVE-2022-1134 Type Confusion in V88.8 0.0186 None reported
High CVE-2022-1310 Chromium: CVE-2022-1310 Use after free in regular expressions8.8 0.0107 None reported
High CVE-2022-1308 Chromium: CVE-2022-1308 Use after free in BFCache8.8 0.0097 None reported
High CVE-2022-1314 Chromium: CVE-2022-1314 Type Confusion in V88.8 0.0097 None reported
High CVE-2022-1125 Chromium: CVE-2022-1125 Use after free in Portals8.8 0.0093 None reported
High CVE-2022-1127 Chromium: CVE-2022-1127 Use after free in QR Code Generator8.8 0.0092 None reported
High CVE-2022-1131 Chromium: CVE-2022-1131 Use after free in Cast UI8.8 0.0091 None reported
High CVE-2022-1133 Chromium: CVE-2022-1133 Use after free in WebRTC8.8 0.0091 None reported
High CVE-2022-1313 Chromium: CVE-2022-1313 Use after free in tab groups8.8 0.0091 None reported
High CVE-2022-1305 Chromium: CVE-2022-1305 Use after free in storage8.8 0.0090 None reported
High CVE-2022-1311 chromium: Use after free in shell in Google Chrome on ChromeOS prior to 100.0.4896.88 allowed a remote attacker to potentially...8.8 0.0090 None reported
High CVE-2022-1135 Chromium: CVE-2022-1135 Use after free in Shopping Cart8.8 0.0089 None reported
High CVE-2022-1143 Chromium: CVE-2022-1143 Heap buffer overflow in WebUI8.8 0.0089 None reported
High CVE-2022-1141 chromium: Use after free in File Manager in Google Chrome prior to 100.0.4896.60 allowed a remote attacker who convinced a user...8.8 0.0086 None reported
High CVE-2022-1130 Chromium: CVE-2022-1130 Insufficient validation of untrusted input in WebOTP8.1 0.0085 None reported
High CVE-2022-1142 chromium: Heap buffer overflow in WebUI in Google Chrome prior to 100.0.4896.60 allowed a remote attacker who convinced a user...8.8 0.0081 None reported
High CVE-2022-2399 chromium: Use after free in WebGPU in Google Chrome prior to 100.0.4896.88 allowed a remote attacker to potentially exploit hea...8.8 0.0074 None reported
High CVE-2022-1144 chromium: Use after free in WebUI in Google Chrome prior to 100.0.4896.60 allowed a remote attacker who convinced a user to eng...8.8 0.0073 None reported
High CVE-2022-1145 Chromium: CVE-2022-1145 Use after free in Extensions7.5 0.0068 None reported
High CVE-2022-1136 Chromium: CVE-2022-1136 Use after free in Tab Strip8.8 0.0064 None reported
Routine CVE-2022-1139 Chromium: CVE-2022-1139 Inappropriate implementation in Background Fetch API6.5 0.0093 None reported
Showing 1 to 25 of 34 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.