VYPR

rpm package

suse/chromium&distro=SUSE Package Hub 12 SP2

pkg:rpm/suse/chromium&distro=SUSE%20Package%20Hub%2012%20SP2

Vulnerabilities (343)

  • CVE-2019-5770Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Insufficient input validation in WebGL in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

  • CVE-2019-5769Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect handling of invalid end character position when front rendering in Blink in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • CVE-2019-5768Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    DevTools API not correctly gating on extension capability in DevTools in Google Chrome prior to 72.0.3626.81 allowed an attacker who convinced a user to install a malicious extension to read local files via a crafted Chrome Extension.

  • CVE-2019-5767Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Insufficient protection of permission UI in WebAPKs in Google Chrome on Android prior to 72.0.3626.81 allowed an attacker who convinced the user to install a malicious application to access privacy/security sensitive web APIs via a crafted APK.

  • CVE-2019-5766Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect handling of origin taint checking in Canvas in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to leak cross-origin data via a crafted HTML page.

  • CVE-2019-5765Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    An exposed debugging endpoint in the browser in Google Chrome on Android prior to 72.0.3626.81 allowed a local attacker to obtain potentially sensitive information from process memory via a crafted Intent.

  • CVE-2019-5764Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect pointer management in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • CVE-2019-5763Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Failure to check error conditions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • CVE-2019-5762Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted PDF file.

  • CVE-2019-5761Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect object lifecycle management in SwiftShader in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • CVE-2019-5760Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Insufficient checks of pointer validity in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • CVE-2019-5759Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect lifetime handling in HTML select elements in Google Chrome on Android and Mac prior to 72.0.3626.81 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.

  • CVE-2019-5758Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect object lifecycle management in Blink in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

  • CVE-2019-5757Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    An incorrect object type assumption in SVG in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page.

  • CVE-2019-5756Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted PDF file.

  • CVE-2019-5755Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Incorrect handling of negative zero in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page.

  • CVE-2019-5754Feb 19, 2019
    affected < 72.0.3626.96-88.1fixed 72.0.3626.96-88.1

    Implementation error in QUIC Networking in Google Chrome prior to 72.0.3626.81 allowed an attacker running or able to cause use of a proxy server to obtain cleartext of transport encryption via malicious network proxy.

  • CVE-2018-6120Jan 9, 2019
    affected < 66.0.3359.181-55.1fixed 66.0.3359.181-55.1

    An integer overflow that could lead to an attacker-controlled heap out-of-bounds write in PDFium in Google Chrome prior to 66.0.3359.170 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted PDF file.

  • CVE-2018-6117Jan 9, 2019
    affected < 66.0.3359.181-55.1fixed 66.0.3359.181-55.1

    Confusing settings in Autofill in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

  • CVE-2018-6114Jan 9, 2019
    affected < 66.0.3359.181-55.1fixed 66.0.3359.181-55.1

    Incorrect enforcement of CSP for tags in Blink in Google Chrome prior to 66.0.3359.117 allowed a remote attacker to bypass content security policy via a crafted HTML page.

Page 2 of 18