Linux ·
Ubuntu · Package update · January 2, 2023
Ubuntu · Package update · January 2, 2023chromium-codecs-ffmpeg 107.0.5304.87-0ubuntu11.18.04.1: chromium-codecs-ffmpeg 107.0.5304.87-0ubuntu11.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 107.0.5304.87-0ubuntu11.18.04.1, released January 2, 2023, fixes 44 CVEs in chromium-codecs-ffmpeg. One of them is being exploited (CVE-2022-3723); 1 on CISA KEV. Patch Radar priority: Patch now. The product is no longer supported.
Patch now1 on CISA KEVUnsupported product
CVEs closed
44
None rated Critical
Exploited
1
CVE-2022-3723
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.2380
97th percentile
Priority of the 44 CVEs
Patch now 1
Urgent 0
High 28
Routine 15
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 107.0.5304.87-0ubuntu11.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Patch now | CVE-2022-3723 | Chromium: CVE-2022-3723 Type Confusion in V8 | 8.8 | 0.0792 | KEVExploited |
| High | CVE-2022-3654 | Chromium: CVE-2022-3654 Use after free in Layout | 8.8 | 0.2380 | None reported |
| High | CVE-2022-3842 | chromium: Use after free in Passwords in Google Chrome prior to 105.0.5195.125 allowed a remote attacker who had compromised th... | 7.5 | 0.1833 | None reported |
| High | CVE-2022-3656 | Chromium: CVE-2022-3656 Insufficient data validation in File System | 8.8 | 0.0253 | None reported |
| High | CVE-2022-3199 | Chromium: CVE-2022-3199 Use after free in Frames | 8.8 | 0.0242 | None reported |
| High | CVE-2022-3195 | Chromium: CVE-2022-3195 Out of bounds write in Storage | 8.8 | 0.0129 | None reported |
| High | CVE-2022-3196 | Chromium: CVE-2022-3196 Use after free in PDF | 8.8 | 0.0109 | None reported |
| High | CVE-2022-3197 | Chromium: CVE-2022-3197 Use after free in PDF | 8.8 | 0.0108 | None reported |
| High | CVE-2022-3446 | Chromium: CVE-2022-3446 Heap buffer overflow in WebSQL | 8.8 | 0.0101 | None reported |
| High | CVE-2022-3370 | Chromium: CVE-2022-3370 Use after free in Custom Elements | 8.8 | 0.0099 | None reported |
| High | CVE-2022-3373 | Chromium: CVE-2022-3373 Out of bounds write in V8 | 8.8 | 0.0099 | None reported |
| High | CVE-2022-3652 | Chromium: CVE-2022-3652 Type Confusion in V8 | 8.8 | 0.0092 | None reported |
| High | CVE-2022-3445 | Chromium: CVE-2022-3445 Use after free in Skia | 8.8 | 0.0091 | None reported |
| High | CVE-2022-3200 | Chromium: CVE-2022-3200 Heap buffer overflow in Internals | 8.8 | 0.0088 | None reported |
| High | CVE-2022-3653 | Chromium: CVE-2022-3653 Heap buffer overflow in Vulkan | 8.8 | 0.0083 | None reported |
| High | CVE-2022-3308 | Chromium: CVE-2022-3308 Insufficient policy enforcement in Developer Tools | 7.4 | 0.0083 | None reported |
| High | CVE-2022-3448 | Chromium: CVE-2022-3448 Use after free in Permissions API | 8.8 | 0.0082 | None reported |
| High | CVE-2022-3304 | Chromium: CVE-2022-3304 Use after free in CSS | 8.8 | 0.0082 | None reported |
| High | CVE-2022-3450 | Chromium: CVE-2022-3450 Use after free in Peer Connection | 8.8 | 0.0080 | None reported |
| High | CVE-2022-3198 | Chromium: CVE-2022-3198 Use after free in PDF | 8.8 | 0.0078 | None reported |
| High | CVE-2022-3306 | chromium: Use after free in survey in Google Chrome on ChromeOS prior to 106.0.5249.62 allowed a remote attacker to potentially... | 8.8 | 0.0074 | None reported |
| High | CVE-2022-3307 | Chromium: CVE-2022-3307 Use after free in Media | 8.8 | 0.0074 | None reported |
| High | CVE-2022-3315 | Chromium: CVE-2022-3315 Type confusion in Blink | 8.8 | 0.0073 | None reported |
| High | CVE-2022-3305 | chromium: Use after free in survey in Google Chrome on ChromeOS prior to 106.0.5249.62 allowed a remote attacker to potentially... | 8.8 | 0.0072 | None reported |
| High | CVE-2022-3659 | chromium: Use after free in Accessibility in Google Chrome on Chrome OS prior to 107.0.5304.62 allowed a remote attacker who co... | 8.8 | 0.0066 | None reported |
Showing 1 to 25 of 44
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.