Search vulnerabilities

Results 425,989

CVE-2019-5770

chromium-browser: Heap buffer overflow in WebGL

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.

CVSS 3.0 · 8.8 High EPSS 3.0% KEV · Not listed
Vendors
Products
CVE-2019-5769

chromium-browser: Insufficient validation of untrusted input in Blink

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.

CVSS 3.0 · 8.8 High EPSS 1.6% KEV · Not listed
Vendors
Products
CVE-2019-5768

chromium-browser: Insufficient policy enforcement in DevTools

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.

CVSS 3.0 · 6.5 Medium EPSS 1.2% KEV · Not listed
Vendors
Products
CVE-2019-5767

chromium-browser: Incorrect security UI in WebAPKs

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.

CVSS 3.0 · 6.5 Medium EPSS 1.3% KEV · Not listed
Vendors
Products
CVE-2019-5766

chromium-browser: Insufficient policy enforcement in Canvas

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.

CVSS 3.0 · 6.5 Medium EPSS 1.6% KEV · Not listed
Vendors
Products
CVE-2019-5765

chromium-browser: Insufficient policy enforcement in the browser

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.

CVSS 3.0 · 5.5 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2019-5764

chromium-browser: Use after free in WebRTC

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.

CVSS 3.0 · 8.8 High EPSS 1.4% KEV · Not listed
Vendors
Products
CVE-2019-5763

chromium-browser: Insufficient validation of untrusted input in V8

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.

CVSS 3.0 · 8.8 High EPSS 1.6% KEV · Not listed
Vendors
Products
CVE-2019-5762

chromium-browser: Use after free in PDFium

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.

CVSS 3.0 · 8.8 High EPSS 2.8% KEV · Not listed
Vendors
Products
CVE-2019-5760

chromium-browser: Use after free in WebRTC

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.

CVSS 3.0 · 8.8 High EPSS 1.5% KEV · Not listed
Vendors
Products
CVE-2019-5759

chromium-browser: Use after free in HTML select elements

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.

CVSS 3.0 · 9.6 Critical EPSS 1.5% KEV · Not listed
Vendors
Products
CVE-2019-5758

chromium-browser: Use after free in Blink

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.

CVSS 3.0 · 8.8 High EPSS 1.7% KEV · Not listed
Vendors
Products
CVE-2019-5757

chromium-browser: Type Confusion in SVG

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.

CVSS 3.0 · 8.8 High EPSS 1.8% KEV · Not listed
Vendors
Products
CVE-2019-5756

chromium-browser: Use after free in PDFium

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.

CVSS 3.0 · 8.8 High EPSS 2.8% KEV · Not listed
Vendors
Products
CVE-2019-5755

chromium-browser: Inappropriate implementation in V8

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.

CVSS 3.0 · 8.1 High EPSS 1.9% KEV · Not listed
Vendors
Products
CVE-2019-5754

chromium-browser: Inappropriate implementation in QUIC Networking

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.

CVSS 3.0 · 6.5 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2019-5748

In Traccar Server version 4.2, protocol/SpotProtocolDecoder.java might allow XXE attacks.

CVSS 3.0 · 9.8 Critical EPSS 1.7% KEV · Not listed
Vendors
Products
CVE-2019-5739

nodejs: DoS with keep-alive HTTP connection

Keep-alive HTTP and HTTPS connections can remain open and inactive for up to 2 minutes in Node.js 6.16.0 and earlier. Node.js 8.0.0 introduced a dedicated server.keepAliveTimeout which defaults to 5 seconds. The behavior in Node.js 6.16.0 and earlier is a potential Denial of Service (DoS) attack vector. Node.js 6.17.0 introduces server.keepAliveTimeout and the 5-second default.

CVSS 3.1 · 7.5 High EPSS 4.9% KEV · Not listed
Vendors
Products
CVE-2019-5737

nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass

In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1.

CVSS 3.1 · 7.5 High EPSS 16.2% KEV · Not listed
Products