Vulnerabilities > Opensuse > Leap > 15.0
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2019-10-16 | CVE-2019-2945 | Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Networking). | 3.1 |
2019-10-16 | CVE-2019-2933 | Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Libraries). | 3.1 |
2019-10-16 | CVE-2019-2894 | Vulnerability in the Java SE, Java SE Embedded product of Oracle Java SE (component: Security). | 3.7 |
2019-10-14 | CVE-2019-17595 | Out-of-bounds Read vulnerability in multiple products There is a heap-based buffer over-read in the fmt_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012. | 5.4 |
2019-10-14 | CVE-2019-17594 | Out-of-bounds Read vulnerability in multiple products There is a heap-based buffer over-read in the _nc_find_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012. | 5.3 |
2019-10-07 | CVE-2019-17042 | Improper Input Validation vulnerability in multiple products An issue was discovered in Rsyslog v8.1908.0. | 9.8 |
2019-10-07 | CVE-2019-17041 | Out-of-bounds Write vulnerability in multiple products An issue was discovered in Rsyslog v8.1908.0. | 9.8 |
2019-10-04 | CVE-2019-17178 | Memory Leak vulnerability in multiple products HuffmanTree_makeFromFrequencies in lodepng.c in LodePNG through 2019-09-28, as used in WinPR in FreeRDP and other products, has a memory leak because a supplied realloc pointer (i.e., the first argument to realloc) is also used for a realloc return value. | 7.5 |
2019-10-04 | CVE-2019-17177 | Memory Leak vulnerability in multiple products libfreerdp/codec/region.c in FreeRDP through 1.1.x and 2.x through 2.0.0-rc4 has memory leaks because a supplied realloc pointer (i.e., the first argument to realloc) is also used for a realloc return value. | 7.5 |
2019-10-03 | CVE-2019-15165 | Allocation of Resources Without Limits or Throttling vulnerability in multiple products sf-pcapng.c in libpcap before 1.9.1 does not properly validate the PHB header length before allocating memory. | 5.3 |