Vulnerabilities > Out-of-bounds Write
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-07-22 | CVE-2018-13924 | Out-of-bounds Write vulnerability in Qualcomm products Lack of check to prevent the buffer length taking negative values can lead to stack overflow. | 9.8 |
| 2019-07-21 | CVE-2019-14210 | Out-of-bounds Write vulnerability in Foxitsoftware Phantompdf An issue was discovered in Foxit PhantomPDF before 8.3.10. | 7.5 |
| 2019-07-21 | CVE-2019-14209 | Out-of-bounds Write vulnerability in Foxitsoftware Phantompdf An issue was discovered in Foxit PhantomPDF before 8.3.10. | 9.8 |
| 2019-07-19 | CVE-2019-13989 | Out-of-bounds Write vulnerability in Dpic Project Dpic 20190620 dpic 2019.06.20 has a Stack-based Buffer Overflow in the wfloat() function in main.c. | 7.8 |
| 2019-07-19 | CVE-2019-1010238 | Out-of-bounds Write vulnerability in multiple products Gnome Pango 1.42 and later is affected by: Buffer Overflow. | 9.8 |
| 2019-07-18 | CVE-2019-13952 | Out-of-bounds Write vulnerability in Gdnsd The set_ipv6() function in zscan_rfc1035.rl in gdnsd before 2.4.3 and 3.x before 3.2.1 has a stack-based buffer overflow via a long and malformed IPv6 address in zone data. | 9.8 |
| 2019-07-18 | CVE-2019-13951 | Out-of-bounds Write vulnerability in Gdnsd 3.2.0 The set_ipv4() function in zscan_rfc1035.rl in gdnsd 3.x before 3.2.1 has a stack-based buffer overflow via a long and malformed IPv4 address in zone data. | 9.8 |
| 2019-07-18 | CVE-2019-3570 | Out-of-bounds Write vulnerability in Facebook Hiphop Virtual Machine Call to the scrypt_enc() function in HHVM can lead to heap corruption by using specifically crafted parameters (N, r and p). | 9.8 |
| 2019-07-17 | CVE-2019-3973 | Out-of-bounds Write vulnerability in Comodo Antivirus Comodo Antivirus versions 11.0.0.6582 and below are vulnerable to Denial of Service affecting CmdGuard.sys via its filter port "cmdServicePort". | 5.5 |
| 2019-07-17 | CVE-2019-11772 | Out-of-bounds Write vulnerability in Eclipse Openj9 In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the provided byte array is non-null nor that the provided index is in bounds when compiled by the JIT. | 9.8 |