Linux · Ubuntu · Package update · June 27, 2019

chromium-codecs-ffmpeg 69.0.3497.81-0ubuntu0.18.04.1: chromium-codecs-ffmpeg 69.0.3497.81-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)

chromium-codecs-ffmpeg 69.0.3497.81-0ubuntu0.18.04.1, released June 27, 2019, fixes 25 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
25
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0526
92nd percentile

Priority of the 25 CVEs

Patch now 0 Urgent 0 High 0 Routine 25

Fixed package versions

ProductReleaseFixed in
chromium-codecs-ffmpegUbuntu 18.04.6 LTS (bionic)69.0.3497.81-0ubuntu0.18.04.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Routine CVE-2018-16083 chromium-browser: An out of bounds read in forward error correction code in WebRTC in Google Chrome prior to 69.0.3497.81 allowed a rem...n/a 0.0526 None reported
Routine CVE-2018-16071 chromium-browser: A use after free in WebRTC in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit he...n/a 0.0480 None reported
Routine CVE-2018-16065 chromium-browser: A Javascript reentrancy issues that caused a use-after-free in V8 in Google Chrome prior to 69.0.3497.81 allowed a re...n/a 0.0324 None reported
Routine CVE-2018-16068 chromium-browser: Missing validation in Mojo in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially perform a...n/a 0.0194 None reported
Routine CVE-2018-16078 chromium-browser: Unsafe handling of credit card details in Autofill in Google Chrome prior to 69.0.3497.81 allowed a remote attacker t...n/a 0.0185 None reported
Routine CVE-2018-16435 chromium-browser: Little CMS (aka Little Color Management System) 2.9 has an integer overflow in the AllocateDataSet function in cmscga...n/a 0.0174 None reported
Routine CVE-2018-16076 chromium-browser: Missing bounds check in PDFium in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to perform an out of...n/a 0.0167 None reported
Routine CVE-2018-16082 chromium-browser: An out of bounds read in Swiftshader in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially...n/a 0.0156 None reported
Routine CVE-2018-16085 chromium-browser: A use after free in ResourceCoordinator in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potential...n/a 0.0148 None reported
Routine CVE-2018-16066 chromium-browser: A use after free in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit hea...n/a 0.0146 None reported
Routine CVE-2018-16067 chromium-browser: A use after free in WebAudio in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit...n/a 0.0141 None reported
Routine CVE-2018-16080 chromium-browser: A missing check for popup window handling in Fullscreen in Google Chrome on macOS prior to 69.0.3497.81 allowed a rem...n/a 0.0136 None reported
Routine CVE-2018-16088 chromium-browser: A missing check for JS-simulated input events in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attack...n/a 0.0113 None reported
Routine CVE-2018-16084 chromium-browser: The default selected dialog button in CustomHandlers in Google Chrome prior to 69.0.3497.81 allowed a remote attacker...n/a 0.0108 None reported
Routine CVE-2018-16079 chromium-browser: A race condition between permission prompts and navigations in Prompts in Google Chrome prior to 69.0.3497.81 allowed...n/a 0.0107 None reported
Routine CVE-2018-16081 chromium-browser: Allowing the chrome.debugger API to run on file:// URLs in DevTools in Google Chrome prior to 69.0.3497.81 allowed an...n/a 0.0104 None reported
Routine CVE-2018-16087 chromium-browser: Lack of proper state tracking in Permissions in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to bypa...n/a 0.0097 None reported
Routine CVE-2018-16069 chromium-browser: Unintended floating-point error accumulation in SwiftShader in Google Chrome prior to 69.0.3497.81 allowed a remote a...n/a 0.0089 None reported
Routine CVE-2018-16070 chromium-browser: Integer overflows in Skia in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit hea...n/a 0.0088 None reported
Routine CVE-2018-16075 chromium-browser: Insufficient file type enforcement in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to obtai...n/a 0.0088 None reported
Routine CVE-2018-16073 chromium-browser: Insufficient policy enforcement in site isolation in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to...n/a 0.0086 None reported
Routine CVE-2018-16074 chromium-browser: Insufficient policy enforcement in site isolation in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to...n/a 0.0085 None reported
Routine CVE-2018-16072 chromium-browser: A missing origin check related to HLS manifests in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote atta...n/a 0.0078 None reported
Routine CVE-2018-16077 chromium-browser: Object lifecycle issue in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to bypass content se...n/a 0.0072 None reported
Routine CVE-2018-16086 chromium-browser: Insufficient policy enforcement in extensions API in Google Chrome prior to 69.0.3497.81 allowed an attacker who conv...n/a 0.0046 None reported
Showing 1 to 25 of 25 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.