Linux · 
Ubuntu · Package update · April 26, 2021
Ubuntu · Package update · April 26, 2021chromium-codecs-ffmpeg-extra 90.0.4430.72-0ubuntu0.18.04.1: chromium-codecs-ffmpeg-extra 90.0.4430.72-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg-extra 90.0.4430.72-0ubuntu0.18.04.1, released April 26, 2021, fixes 27 CVEs in chromium-codecs-ffmpeg-extra. 2 of them are being exploited (CVE-2021-21220); 2 on CISA KEV. Patch Radar priority: Patch now. The product is no longer supported.
Patch now2 on CISA KEVUnsupported product
CVEs closed
27
None rated Critical
Exploited
2
CVE-2021-21220
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.7044
99th percentile
Priority of the 27 CVEs
Patch now 2
Urgent 0
High 0
Routine 25
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg-extra | Ubuntu 18.04.6 LTS (bionic) | 90.0.4430.72-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Patch now | CVE-2021-21220 | Chromium: CVE-2021-21220 Insufficient validation of untrusted input in V8 for x86_64 | n/a | 0.7044 | KEVExploited |
| Patch now | CVE-2021-21206 | Chromium: CVE-2021-21206 Use after free in Blink | n/a | 0.0931 | KEVExploited |
| Routine | CVE-2021-21215 | Chromium: CVE-2021-21215 Inappropriate implementation in Autofill | n/a | 0.3447 | None reported |
| Routine | CVE-2021-21216 | Chromium: CVE-2021-21216 Inappropriate implementation in Autofill | n/a | 0.2177 | None reported |
| Routine | CVE-2021-21210 | Chromium: CVE-2021-21210 Inappropriate implementation in Network | n/a | 0.0191 | None reported |
| Routine | CVE-2021-21212 | Chromium: CVE-2021-21212 Incorrect security UI in Network Config UI | n/a | 0.0181 | None reported |
| Routine | CVE-2021-21198 | Chromium: CVE-2021-21198 Out of bounds read in IPC | n/a | 0.0179 | None reported |
| Routine | CVE-2021-21203 | Chromium: CVE-2021-21203 Use after free in Blink | n/a | 0.0177 | None reported |
| Routine | CVE-2021-21201 | Chromium: CVE-2021-21201 Use after free in permissions | n/a | 0.0170 | None reported |
| Routine | CVE-2021-21217 | Chromium: CVE-2021-21217 Uninitialized Use in PDFium | n/a | 0.0164 | None reported |
| Routine | CVE-2021-21221 | Chromium: CVE-2021-21221 Insufficient validation of untrusted input in Mojo | n/a | 0.0157 | None reported |
| Routine | CVE-2021-21204 | Chromium: CVE-2021-21204 Use after free in Blink | n/a | 0.0157 | None reported |
| Routine | CVE-2021-21213 | Chromium: CVE-2021-21213 Use after free in WebMIDI | n/a | 0.0152 | None reported |
| Routine | CVE-2021-21205 | Chromium: CVE-2021-21205 Insufficient policy enforcement in navigation | n/a | 0.0147 | None reported |
| Routine | CVE-2021-21208 | Chromium: CVE-2021-21208 Insufficient data validation in QR scanner | n/a | 0.0140 | None reported |
| Routine | CVE-2021-21197 | Chromium: CVE-2021-21197 Heap buffer overflow in TabStrip | n/a | 0.0136 | None reported |
| Routine | CVE-2021-21195 | Chromium: CVE-2021-21195 Use after free in V8 | n/a | 0.0135 | None reported |
| Routine | CVE-2021-21196 | Chromium: CVE-2021-21196 Heap buffer overflow in TabStrip | n/a | 0.0134 | None reported |
| Routine | CVE-2021-21218 | Chromium: CVE-2021-21218 Uninitialized Use in PDFium | n/a | 0.0134 | None reported |
| Routine | CVE-2021-21214 | Chromium: CVE-2021-21214 Use after free in Network API | n/a | 0.0129 | None reported |
| Routine | CVE-2021-21194 | Chromium: CVE-2021-21194 Use after free in screen capture | n/a | 0.0121 | None reported |
| Routine | CVE-2021-21219 | Chromium: CVE-2021-21219 Uninitialized Use in PDFium | n/a | 0.0121 | None reported |
| Routine | CVE-2021-21199 | Chromium: CVE-2021-21199 Use Use after free in Aura | n/a | 0.0115 | None reported |
| Routine | CVE-2021-21202 | Chromium: CVE-2021-21202 Use after free in extensions | n/a | 0.0103 | None reported |
| Routine | CVE-2021-21211 | Chromium: CVE-2021-21211 Inappropriate implementation in Navigation | n/a | 0.0102 | 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.