Linux · Ubuntu · Package update · December 10, 2019

chromium-chromedriver 75.0.3770.142-0ubuntu0.18.04.1: chromium-chromedriver 75.0.3770.142-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)

chromium-chromedriver 75.0.3770.142-0ubuntu0.18.04.1, released December 10, 2019, fixes 16 CVEs in chromium-chromedriver. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

RoutineUnsupported product
CVEs closed
16
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0194
80th percentile

Priority of the 16 CVEs

Patch now 0 Urgent 0 High 0 Routine 16

Fixed package versions

ProductReleaseFixed in
chromium-chromedriverUbuntu 18.04.6 LTS (bionic)75.0.3770.142-0ubuntu0.18.04.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Routine CVE-2019-5831 chromium-browser: Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit...n/a 0.0194 None reported
Routine CVE-2019-5835 chromium-browser: Object lifecycle issue in SwiftShader in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially...n/a 0.0162 None reported
Routine CVE-2019-5837 chromium-browser: Resource size information leakage in Blink in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to leak c...n/a 0.0152 None reported
Routine CVE-2019-5836 chromium-browser: Heap buffer overflow in ANGLE in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit...n/a 0.0143 None reported
Routine CVE-2019-5830 chromium-browser: Insufficient policy enforcement in CORS in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to leak cros...n/a 0.0137 None reported
Routine CVE-2019-5828 chromium-browser: Object lifecycle issue in ServiceWorker in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potential...n/a 0.0137 None reported
Routine CVE-2019-5829 chromium-browser: Integer overflow in download manager in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially...n/a 0.0127 None reported
Routine CVE-2019-5839 chromium-browser: Excessive data validation in URL parser in Google Chrome prior to 75.0.3770.80 allowed a remote attacker who convince...n/a 0.0125 None reported
Routine CVE-2019-5832 chromium-browser: Insufficient policy enforcement in XMLHttpRequest in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to...n/a 0.0125 None reported
Routine CVE-2019-5866 chromium-browser: Out of bounds memory access in JavaScript in Google Chrome prior to 75.0.3770.142 allowed a remote attacker to potent...n/a 0.0111 None reported
Routine CVE-2019-5840 chromium-browser: Incorrect security UI in popup blocker in Google Chrome on iOS prior to 75.0.3770.80 allowed a remote attacker to byp...n/a 0.0104 None reported
Routine CVE-2019-5833 chromium-browser: Incorrect dialog box scoping in browser in Google Chrome on Android prior to 75.0.3770.80 allowed a remote attacker t...n/a 0.0096 None reported
Routine CVE-2019-5847 chromium-browser: Inappropriate implementation in JavaScript in Google Chrome prior to 75.0.3770.142 allowed a remote attacker to poten...n/a 0.0086 None reported
Routine CVE-2019-5841 chromium-browser: Out of bounds memory access in JavaScript in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potenti...n/a 0.0082 None reported
Routine CVE-2019-5838 chromium-browser: Insufficient policy enforcement in extensions API in Google Chrome prior to 75.0.3770.80 allowed an attacker who conv...n/a 0.0077 None reported
Routine CVE-2019-5848 chromium-browser: Incorrect font handling in autofill in Google Chrome prior to 75.0.3770.142 allowed a remote attacker to obtain poten...n/a 0.0049 None reported
Showing 1 to 16 of 16 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.