Linux · 
Ubuntu · Package update · August 28, 2018
Ubuntu · Package update · August 28, 2018chromium-codecs-ffmpeg 62.0.3202.89-0ubuntu1.1386: chromium-codecs-ffmpeg 62.0.3202.89-0ubuntu1.1386 for Ubuntu 18.04.6 LTS (bionic)
chromium-codecs-ffmpeg 62.0.3202.89-0ubuntu1.1386, released August 28, 2018, fixes 4 CVEs in chromium-codecs-ffmpeg. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.
RoutineUnsupported product
CVEs closed
4
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0489
92nd percentile
Priority of the 4 CVEs
Patch now 0
Urgent 0
High 0
Routine 4
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| chromium-codecs-ffmpeg | Ubuntu 18.04.6 LTS (bionic) | 62.0.3202.89-0ubuntu1.1386 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2017-15399 | chromium-browser: A use after free in V8 in Google Chrome prior to 62.0.3202.89 allowed a remote attacker to potentially exploit heap c... | n/a | 0.0489 | None reported |
| Routine | CVE-2017-15398 | chromium-browser: A stack buffer overflow in the QUIC networking stack in Google Chrome prior to 62.0.3202.89 allowed a remote attacker... | n/a | 0.0383 | None reported |
| Routine | CVE-2017-15396 | chromium-browser: A stack buffer overflow in NumberingSystem in International Components for Unicode (ICU) for C/C++ before 60.2, as us... | n/a | 0.0220 | None reported |
| Routine | CVE-2017-15406 | chromium-codecs-ffmpeg: A stack buffer overflow in V8 in Google Chrome prior to 62.0.3202.75 allowed a remote attacker to perform an out of b... | n/a | 0.0088 | None reported |
Showing 1 to 4 of 4
1
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.