Linux ·
Ubuntu · Package update · January 2, 2023
Ubuntu · Package update · January 2, 2023chromium-codecs-ffmpeg-extra 72.0.3626.119-0ubuntu0.18.04.1: chromium-codecs-ffmpeg-extra 72.0.3626.119-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg-extra 72.0.3626.119-0ubuntu0.18.04.1, released January 2, 2023, fixes 31 CVEs in chromium-codecs-ffmpeg-extra. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.
HighUnsupported product
CVEs closed
31
None rated Critical
Exploited
0
None reported
Highest CVSS
7.4
Base score, 0 to 10
Highest EPSS
0.1336
96th percentile
Priority of the 31 CVEs
Patch now 0
Urgent 0
High 1
Routine 30
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg-extra | Ubuntu 18.04.6 LTS (bionic) | 72.0.3626.119-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2019-13768 | chromium-browser: Use after free in FileAPI in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially perform a s... | 7.4 | 0.0094 | None reported |
| Routine | CVE-2019-5782 | chromium-browser: Incorrect optimization assumptions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute... | n/a | 0.1336 | None reported |
| Routine | CVE-2019-5770 | chromium-browser: Insufficient input validation in WebGL in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform an... | n/a | 0.0302 | None reported |
| Routine | CVE-2019-5756 | chromium-browser: Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attack... | n/a | 0.0282 | None reported |
| Routine | CVE-2019-5762 | chromium-browser: Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attack... | n/a | 0.0282 | None reported |
| Routine | CVE-2019-5779 | chromium-browser: Insufficient policy validation in ServiceWorker in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to b... | n/a | 0.0259 | None reported |
| Routine | CVE-2019-5755 | chromium-browser: Incorrect handling of negative zero in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform... | n/a | 0.0191 | None reported |
| Routine | CVE-2019-5773 | chromium-browser: Insufficient origin validation in IndexedDB in Google Chrome prior to 72.0.3626.81 allowed a remote attacker who had... | n/a | 0.0182 | None reported |
| Routine | CVE-2019-5757 | chromium-browser: An incorrect object type assumption in SVG in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potent... | n/a | 0.0179 | None reported |
| Routine | CVE-2019-5772 | chromium-browser: Sharing of objects over calls into JavaScript runtime in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remo... | n/a | 0.0173 | None reported |
| Routine | CVE-2019-5758 | chromium-browser: Incorrect object lifecycle management in Blink in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to po... | n/a | 0.0167 | None reported |
| Routine | CVE-2019-5766 | chromium-browser: Incorrect handling of origin taint checking in Canvas in Google Chrome prior to 72.0.3626.81 allowed a remote attacke... | n/a | 0.0163 | None reported |
| Routine | CVE-2019-5763 | chromium-browser: Failure to check error conditions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potential... | n/a | 0.0163 | None reported |
| Routine | CVE-2019-5769 | chromium-browser: Incorrect handling of invalid end character position when front rendering in Blink in Google Chrome prior to 72.0.362... | n/a | 0.0161 | None reported |
| Routine | CVE-2019-5784 | chromium-browser: Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potenti... | n/a | 0.0155 | None reported |
| Routine | CVE-2019-5774 | chromium-browser: Omission of the .desktop filetype from the Safe Browsing checklist in SafeBrowsing in Google Chrome on Linux prior to... | n/a | 0.0151 | None reported |
| Routine | CVE-2019-5775 | chromium-browser: Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attac... | n/a | 0.0147 | None reported |
| Routine | CVE-2019-5776 | chromium-browser: Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attac... | n/a | 0.0147 | None reported |
| Routine | CVE-2019-5777 | chromium-browser: Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attac... | n/a | 0.0147 | None reported |
| Routine | CVE-2019-5781 | chromium-browser: Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attac... | n/a | 0.0147 | None reported |
| Routine | CVE-2019-5759 | chromium-browser: Incorrect lifetime handling in HTML select elements in Google Chrome on Android and Mac prior to 72.0.3626.81 allowed... | n/a | 0.0146 | None reported |
| Routine | CVE-2019-5760 | chromium-browser: Insufficient checks of pointer validity in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to... | n/a | 0.0146 | None reported |
| Routine | CVE-2019-5764 | chromium-browser: Incorrect pointer management in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentiall... | n/a | 0.0142 | None reported |
| Routine | CVE-2019-5767 | chromium-browser: Insufficient protection of permission UI in WebAPKs in Google Chrome on Android prior to 72.0.3626.81 allowed an atta... | n/a | 0.0134 | None reported |
| Routine | CVE-2019-5768 | chromium-browser: DevTools API not correctly gating on extension capability in DevTools in Google Chrome prior to 72.0.3626.81 allowed... | n/a | 0.0119 | None reported |
Showing 1 to 25 of 31
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.