CVEs published February 19, 2019
38 CVEs were published on February 19, 2019: 0 critical, 0 high.
- Published
- 38
- Critical
- 0
- High
- 0
- Medium
- 2
- Low
- 0
- Unrated
- 36
- Now in CISA KEV
- 0
- Fix available
- 30
Most affected products
- Google Chrome
- 30
- Kaspersky Lab CODESYS V3 products
- 2
- IBM WebSphere Application Server
- 1
- SonicWall SonicOS · SonicWall SonicOSv
- 1
- The QEMU Project qemu
- 1
Medium, low and unrated 38
- CVE-2018-20025Use of Insufficiently Random Values exists in CODESYS V3 products versions prior V3.5.14.0.Kaspersky Lab CODESYS V3 products
- CVE-2018-20026Improper Communication Address Filtering exists in CODESYS V3 products versions prior V3.5.14.0.Kaspersky Lab CODESYS V3 products
- CVE-2018-9867In SonicWall SonicOS, administrators without full permissions can download imported certificates.SonicWall SonicOS · SonicWall SonicOSv
- CVE-2018-1996IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 could provide weaker than expected security, caused by the improper TLS configuratioIBM WebSphere Application Server
- CVE-2019-5754Implementation 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 sGoogle Chrome
- CVE-2019-5755Incorrect handling of negative zero in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform arbitrary read/write vGoogle Chrome
- CVE-2019-5756Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitraryGoogle Chrome
- CVE-2019-5757An incorrect object type assumption in SVG in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit object coGoogle Chrome
- CVE-2019-5758Incorrect object lifecycle management in Blink in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap Google Chrome
- CVE-2019-5759Incorrect lifetime handling in HTML select elements in Google Chrome on Android and Mac prior to 72.0.3626.81 allowed a remote attacker to pGoogle Chrome
- CVE-2019-5760Insufficient checks of pointer validity in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heGoogle Chrome
- CVE-2019-5761Incorrect object lifecycle management in SwiftShader in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploitGoogle Chrome
- CVE-2019-5762Inappropriate memory management when caching in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitraryGoogle Chrome
- CVE-2019-5763Failure to check error conditions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruptGoogle Chrome
- CVE-2019-5764Incorrect pointer management in WebRTC in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially exploit heap corruptiGoogle Chrome
- CVE-2019-5765An exposed debugging endpoint in the browser in Google Chrome on Android prior to 72.0.3626.81 allowed a local attacker to obtain potentiallGoogle Chrome
- CVE-2019-5766Incorrect handling of origin taint checking in Canvas in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to leak cross-origin Google Chrome
- CVE-2019-5767Insufficient protection of permission UI in WebAPKs in Google Chrome on Android prior to 72.0.3626.81 allowed an attacker who convinced the Google Chrome
- CVE-2019-5768DevTools API not correctly gating on extension capability in DevTools in Google Chrome prior to 72.0.3626.81 allowed an attacker who convincGoogle Chrome
- CVE-2019-5769Incorrect handling of invalid end character position when front rendering in Blink in Google Chrome prior to 72.0.3626.81 allowed a remote aGoogle Chrome
- CVE-2019-5770Insufficient input validation in WebGL in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform an out of bounds memory rGoogle Chrome
- CVE-2019-5771An incorrect JIT of GLSL shaders in SwiftShader in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitrary code vGoogle Chrome
- CVE-2019-5772Sharing of objects over calls into JavaScript runtime in PDFium in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentiaGoogle Chrome
- CVE-2019-5773Insufficient origin validation in IndexedDB in Google Chrome prior to 72.0.3626.81 allowed a remote attacker who had compromised the rendereGoogle Chrome
- CVE-2019-5774Omission of the .desktop filetype from the Safe Browsing checklist in SafeBrowsing in Google Chrome on Linux prior to 72.0.3626.81 allowed aGoogle Chrome
- CVE-2019-5775Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to spoof the contenGoogle Chrome
- CVE-2019-5776Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to spoof the contenGoogle Chrome
- CVE-2019-5777Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to spoof the contenGoogle Chrome
- CVE-2019-5778A missing case for handling special schemes in permission request checks in Extensions in Google Chrome prior to 72.0.3626.81 allowed an attGoogle Chrome
- CVE-2019-5779Insufficient policy validation in ServiceWorker in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to bypass navigation restriGoogle Chrome
- CVE-2019-5780Insufficient restrictions on what can be done with Apple Events in Google Chrome on macOS prior to 72.0.3626.81 allowed a local attacker to Google Chrome
- CVE-2019-5781Incorrect handling of a confusable character in Omnibox in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to spoof the contenGoogle Chrome
- CVE-2019-5782Incorrect optimization assumptions in V8 in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to execute arbitrary code inside aGoogle Chrome
- CVE-2019-5783Missing URI encoding of untrusted input in DevTools in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to perform a Dangling MGoogle Chrome
- CVE-2019-8939data/interfaces/default/history.html in Tautulli 2.1.26 has XSS via a crafted Plex username that is mishandled when constructing the History
- CVE-2019-8935Collabtive 3.1 allows XSS via the manageuser.php?action=profile id parameter.
- CVE-2019-3812QEMU, through version 2.10 and through version 3.1.0, is vulnerable to an out-of-bounds read of up to 128 bytes in the hw/i2c/i2c-ddc.c:i2c_The QEMU Project qemu
- CVE-2019-8933In DedeCMS 5.7SP2, attackers can upload a .php file to the uploads/ directory (without being blocked by the Web Application Firewall), and t