Linux ·
Ubuntu · Package update · December 11, 2018
Ubuntu · Package update · December 11, 2018chromium-codecs-ffmpeg 71.0.3578.80-0ubuntu0.18.04.1: chromium-codecs-ffmpeg 71.0.3578.80-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 71.0.3578.80-0ubuntu0.18.04.1, released December 11, 2018, fixes 27 CVEs in chromium-codecs-ffmpeg. One of them is being exploited (CVE-2018-17480); 1 on CISA KEV. Patch Radar priority: Patch now. The product is no longer supported.
Patch now1 on CISA KEVUnsupported product
CVEs closed
27
None rated Critical
Exploited
1
CVE-2018-17480
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.3564
98th percentile
Priority of the 27 CVEs
Patch now 1
Urgent 0
High 1
Routine 25
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 71.0.3578.80-0ubuntu0.18.04.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Patch now | CVE-2018-17480 | chromium-browser: Execution of user supplied Javascript during array deserialization leading to an out of bounds write in V8 in Google... | n/a | 0.3564 | KEVExploited |
| High | CVE-2018-18356 | chromium-browser: An integer overflow in path handling lead to a use after free in Skia in Google Chrome prior to 71.0.3578.80 allowed... | 8.8 | 0.0328 | None reported |
| Routine | CVE-2018-18335 | chromium-browser: Heap buffer overflow in Skia in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentially exploit... | n/a | 0.0390 | None reported |
| Routine | CVE-2018-18342 | chromium-browser: Execution of user supplied Javascript during object deserialization can update object length leading to an out of bou... | n/a | 0.0265 | None reported |
| Routine | CVE-2018-18351 | chromium-browser: Lack of proper validation of ancestor frames site when sending lax cookies in Navigation in Google Chrome prior to 71... | n/a | 0.0255 | None reported |
| Routine | CVE-2018-18337 | chromium-browser: Incorrect handling of stylesheets leading to a use after free in Blink in Google Chrome prior to 71.0.3578.80 allowed... | n/a | 0.0168 | None reported |
| Routine | CVE-2018-17481 | chromium-browser: Incorrect object lifecycle handling in PDFium in Google Chrome prior to 71.0.3578.98 allowed a remote attacker to pot... | n/a | 0.0161 | None reported |
| Routine | CVE-2018-18336 | chromium-browser: Incorrect object lifecycle in PDFium in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentially... | n/a | 0.0153 | None reported |
| Routine | CVE-2018-18344 | chromium-browser: Inappropriate allowance of the setDownloadBehavior devtools protocol feature in Extensions in Google Chrome prior to... | n/a | 0.0150 | None reported |
| Routine | CVE-2018-18341 | chromium-browser: An integer overflow leading to a heap buffer overflow in Blink in Google Chrome prior to 71.0.3578.80 allowed a remot... | n/a | 0.0147 | None reported |
| Routine | CVE-2018-18345 | chromium-browser: Incorrect handling of blob URLS in Site Isolation in Google Chrome prior to 71.0.3578.80 allowed a remote attacker wh... | n/a | 0.0145 | None reported |
| Routine | CVE-2018-18338 | chromium-browser: Incorrect, thread-unsafe use of SkImage in Canvas in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to... | n/a | 0.0142 | None reported |
| Routine | CVE-2018-18339 | chromium-browser: Incorrect object lifecycle in WebAudio in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentiall... | n/a | 0.0142 | None reported |
| Routine | CVE-2018-18354 | chromium-browser: Insufficient validate of external protocols in Shell Integration in Google Chrome on Windows prior to 71.0.3578.80 al... | n/a | 0.0142 | None reported |
| Routine | CVE-2018-18359 | chromium-browser: Incorrect handling of Reflect.construct in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to per... | n/a | 0.0141 | None reported |
| Routine | CVE-2018-18352 | chromium-browser: Service works could inappropriately gain access to cross origin audio in Media in Google Chrome prior to 71.0.3578.80... | n/a | 0.0139 | None reported |
| Routine | CVE-2018-18340 | chromium-browser: Incorrect object lifecycle in MediaRecorder in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to poten... | n/a | 0.0139 | None reported |
| Routine | CVE-2018-18347 | chromium-browser: Incorrect handling of failed navigations with invalid URLs in Navigation in Google Chrome prior to 71.0.3578.80 allow... | n/a | 0.0139 | None reported |
| Routine | CVE-2018-18343 | chromium-browser: Incorrect handing of paths leading to a use after free in Skia in Google Chrome prior to 71.0.3578.80 allowed a remot... | n/a | 0.0138 | None reported |
| Routine | CVE-2018-18350 | chromium-browser: Incorrect handling of CSP enforcement during navigations in Blink in Google Chrome prior to 71.0.3578.80 allowed a re... | n/a | 0.0138 | None reported |
| Routine | CVE-2018-18353 | chromium-browser: Failure to dismiss http auth dialogs on navigation in Network Authentication in Google Chrome on Android prior to 71.... | n/a | 0.0137 | None reported |
| Routine | CVE-2018-18346 | chromium-browser: Incorrect handling of alert box display in Blink in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to... | n/a | 0.0133 | None reported |
| Routine | CVE-2018-18355 | chromium-browser: Incorrect handling of confusable characters in URL Formatter in Google Chrome prior to 71.0.3578.80 allowed a remote... | n/a | 0.0115 | None reported |
| Routine | CVE-2018-18357 | chromium-browser: Incorrect handling of confusable characters in URL Formatter in Google Chrome prior to 71.0.3578.80 allowed a remote... | n/a | 0.0115 | None reported |
| Routine | CVE-2018-18348 | chromium-browser: Incorrect handling of bidirectional domain names with RTL characters in Omnibox in Google Chrome prior to 71.0.3578.8... | n/a | 0.0111 | 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.