p PatchFirst

PatchFirst · Latest vulnerabilities

chromium-browser vulnerabilities · Page 69

Vulnerabilities published for chromium-browser in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 1499

  1. CVE-2018-18349

    Medium · CVSS 6.5EPSS 0.98%Fix available

    CVE-2018-18349

    Remote frame navigations was incorrectly permitted to local resources in Blink in Google Chrome prior to 71.0.3578.80 allowed an attacker who convinced a user to install a malicious extension to access files on the local file system via a crafted Chrome Extension.

    • Update to 71.0.3578.80-0ubuntu0.18.04.1
    Published Updated
  2. CVE-2018-18344

    Medium · CVSS 6.5EPSS 1.5%Fix available

    CVE-2018-18344

    Inappropriate allowance of the setDownloadBehavior devtools protocol feature in Extensions in Google Chrome prior to 71.0.3578.80 allowed a remote attacker with control of an installed extension to access files on the local file system via a crafted Chrome Extension.

    • Update to 71.0.3578.80-0ubuntu0.18.04.1
    Published Updated
  3. CVE-2018-18342

    High · CVSS 8.8EPSS 2.65%Fix available

    CVE-2018-18342

    Execution of user supplied Javascript during object deserialization can update object length leading to an out of bounds write in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.

    • Update to 71.0.3578.80-0ubuntu0.18.04.1
    Published Updated
  4. CVE-2018-6152

    Critical · CVSS 9.6EPSS 1.31%Fix available

    CVE-2018-6152

    The implementation of the Page.downloadBehavior backend unconditionally marked downloaded files as safe, regardless of file type in Google Chrome prior to 66.0.3359.117 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted HTML page and user interaction.

    • Update to 68.0.3440.75-0ubuntu0.18.04.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →