Linux · Ubuntu · Package update · November 2, 2021

chromium-browser 67.0.3396.99-0ubuntu0.18.04.1: chromium-browser 67.0.3396.99-0ubuntu0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)

chromium-browser 67.0.3396.99-0ubuntu0.18.04.1, released November 2, 2021, fixes 26 CVEs in chromium-browser. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

RoutineUnsupported product
CVEs closed
26
None rated Critical
Exploited
0
None reported
Highest CVSS
n/a
No CVSS score published
Highest EPSS
0.0767
94th percentile

Priority of the 26 CVEs

Patch now 0 Urgent 0 High 0 Routine 26

Fixed package versions

ProductReleaseFixed in
chromium-browserUbuntu 18.04.6 LTS (bionic)67.0.3396.99-0ubuntu0.18.04.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
Routine CVE-2018-6126 chromium-browser: A precision error in Skia in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bound...n/a 0.0767 None reported
Routine CVE-2018-6130 chromium-browser: Incorrect handling of object lifetimes in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to...n/a 0.0271 None reported
Routine CVE-2018-6129 chromium-browser: Out of bounds array access in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially...n/a 0.0271 None reported
Routine CVE-2018-6140 chromium-browser: Allowing the chrome.debugger API to attach to Web UI pages in DevTools in Google Chrome prior to 67.0.3396.62 allowed...n/a 0.0264 None reported
Routine CVE-2018-6124 chromium-codecs-ffmpeg: Type confusion in ReadableStreams in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potent...n/a 0.0193 None reported
Routine CVE-2018-6139 chromium-browser: Insufficient target checks on the chrome.debugger API in DevTools in Google Chrome prior to 67.0.3396.62 allowed an a...n/a 0.0192 None reported
Routine CVE-2018-6137 chromium-codecs-ffmpeg-extra: CSS Paint API in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to leak cross-origin data via...n/a 0.0190 None reported
Routine CVE-2018-6123 chromium-browser: A use after free in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially exploit hea...n/a 0.0188 None reported
Routine CVE-2018-6127 chromium-browser: Early free of object in use in IndexDB in Google Chrome prior to 67.0.3396.62 allowed a remote attacker who had compr...n/a 0.0179 None reported
Routine CVE-2018-6141 chromium-browser: Insufficient validation of an image filter in Skia in Google Chrome prior to 67.0.3396.62 allowed a remote attacker w...n/a 0.0167 None reported
Routine CVE-2018-6143 chromium-browser: Insufficient validation in V8 in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of b...n/a 0.0160 None reported
Routine CVE-2018-6144 chromium-browser: Off-by-one error in PDFium in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of boun...n/a 0.0151 None reported
Routine CVE-2018-6135 chromium-browser: Lack of clearing the previous site before loading alerts from a new one in Blink in Google Chrome prior to 67.0.3396....n/a 0.0143 None reported
Routine CVE-2018-6133 chromium-browser: Incorrect handling of confusable characters in URL Formatter in Google Chrome prior to 67.0.3396.62 allowed a remote...n/a 0.0142 None reported
Routine CVE-2018-6131 chromium-browser: Object lifecycle issue in WebAssembly in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to potentially...n/a 0.0088 None reported
Routine CVE-2018-6128 chromium-browser: Incorrect URL parsing in WebKit in Google Chrome on iOS prior to 67.0.3396.62 allowed a remote attacker to perform do...n/a 0.0088 None reported
Routine CVE-2018-6132 chromium-browser: Uninitialized data in WebRTC in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to obtain potentially s...n/a 0.0087 None reported
Routine CVE-2018-6134 chromium-browser: Information leak in Blink in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to bypass no-referrer poli...n/a 0.0085 None reported
Routine CVE-2018-6142 chromium-browser: Array bounds check failure in V8 in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out o...n/a 0.0083 None reported
Routine CVE-2018-6136 chromium-browser: Missing type check in V8 in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds...n/a 0.0075 None reported
Routine CVE-2018-6149 chromium-browser: Type confusion in JavaScript in Google Chrome prior to 67.0.3396.87 allowed a remote attacker to perform an out of bo...n/a 0.0072 None reported
Routine CVE-2018-6145 chromium-browser: Insufficient data validation in HTML parser in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to bypas...n/a 0.0071 None reported
Routine CVE-2018-6148 chromium-browser: Incorrect implementation in Content Security Policy in Google Chrome prior to 67.0.3396.79 allowed a remote attacker...n/a 0.0069 None reported
Routine CVE-2018-6138 chromium-browser: Insufficient policy enforcement in Extensions API in Google Chrome prior to 67.0.3396.62 allowed an attacker who conv...n/a 0.0063 None reported
Routine CVE-2018-6125 chromium-browser: Insufficient policy enforcement in USB in Google Chrome on Windows prior to 67.0.3396.62 allowed a remote attacker to...n/a 0.0063 None reported
Showing 1 to 25 of 26 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.