Total
13684 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2017-1000375 | 1 Netbsd | 1 Netbsd | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| NetBSD maps the run-time link-editor ld.so directly below the stack region, even if ASLR is enabled, this allows attackers to more easily manipulate memory leading to arbitrary code execution. This affects NetBSD 7.1 and possibly earlier versions. | |||||
| CVE-2017-1000366 | 8 Debian, Gnu, Mcafee and 5 more | 20 Debian Linux, Glibc, Web Gateway and 17 more | 2026-06-17 | 7.2 HIGH | 7.8 HIGH |
| glibc contains a vulnerability that allows specially crafted LD_LIBRARY_PATH values to manipulate the heap/stack, causing them to alias, potentially resulting in arbitrary code execution. Please note that additional hardening changes have been made to glibc to prevent manipulation of stack and heap memory but these issues are not directly exploitable, as such they have not been given a CVE. This affects glibc 2.25 and earlier. | |||||
| CVE-2017-1000364 | 1 Linux | 1 Linux Kernel | 2026-06-17 | 6.2 MEDIUM | 7.4 HIGH |
| An issue was discovered in the size of the stack guard page on Linux, specifically a 4k stack guard page is not sufficiently large and can be "jumped" over (the stack guard page is bypassed), this affects Linux Kernel versions 4.11.5 and earlier (the stackguard page was introduced in 2010). | |||||
| CVE-2017-1000257 | 2 Debian, Haxx | 2 Debian Linux, Libcurl | 2026-06-17 | 6.4 MEDIUM | 9.1 CRITICAL |
| An IMAP FETCH response line indicates the size of the returned data, in number of bytes. When that response says the data is zero bytes, libcurl would pass on that (non-existing) data with a pointer and the size (zero) to the deliver-data function. libcurl's deliver-data function treats zero as a magic number and invokes strlen() on the data to figure out the length. The strlen() is called on a heap based buffer that might not be zero terminated so libcurl might read beyond the end of it into whatever memory lies after (or just crash) and then deliver that to the application as if it was actually downloaded. | |||||
| CVE-2017-1000254 | 1 Haxx | 1 Libcurl | 2026-06-17 | 5.0 MEDIUM | 7.5 HIGH |
| libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote. | |||||
| CVE-2017-1000253 | 3 Centos, Linux, Redhat | 3 Centos, Linux Kernel, Enterprise Linux | 2026-06-17 | 7.2 HIGH | 7.8 HIGH |
| Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm->mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm->mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm->mmap_base into the are that is supposed to be the "gap" between the stack and the binary. | |||||
| CVE-2017-1000249 | 1 File Project | 1 File | 2026-06-17 | 2.1 LOW | 5.5 MEDIUM |
| An issue in file() was introduced in commit 9611f31313a93aa036389c5f3b15eea53510d4d1 (Oct 2016) lets an attacker overwrite a fixed 20 bytes stack buffer with a specially crafted .notes section in an ELF binary. This was fixed in commit 35c94dc6acc418f1ad7f6241a6680e5327495793 (Aug 2017). | |||||
| CVE-2017-1000218 | 1 Hfiref0x | 1 Lightftp | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| LightFTP version 1.1 is vulnerable to a buffer overflow in the "writelogentry" function resulting a denial of services or a remote code execution. | |||||
| CVE-2017-1000210 | 1 Altran | 1 Picotcp | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| picoTCP (versions 1.7.0 - 1.5.0) is vulnerable to stack buffer overflow resulting in code execution or denial of service attack | |||||
| CVE-2017-1000206 | 1 Htslib | 1 Htslib | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| samtools htslib library version 1.4.0 and earlier is vulnerable to buffer overflow in the CRAM rANS codec resulting in potential arbitrary code execution | |||||
| CVE-2017-1000198 | 1 Tcmu-runner Project | 1 Tcmu-runner | 2026-06-17 | 5.0 MEDIUM | 7.5 HIGH |
| tcmu-runner daemon version 0.9.0 to 1.2.0 is vulnerable to invalid memory references in the handler_glfs.so handler resulting in denial of service | |||||
| CVE-2017-1000187 | 1 Swftools | 1 Swftools | 2026-06-17 | 4.3 MEDIUM | 7.8 HIGH |
| In SWFTools, an address access exception was found in pdf2swf. FoFiTrueType::writeTTF() | |||||
| CVE-2017-1000186 | 1 Swftools | 1 Swftools | 2026-06-17 | 4.3 MEDIUM | 5.5 MEDIUM |
| In SWFTools, a stack overflow was found in pdf2swf. | |||||
| CVE-2017-1000185 | 1 Swftools | 1 Swftools | 2026-06-17 | 4.3 MEDIUM | 5.5 MEDIUM |
| In SWFTools, a memcpy buffer overflow was found in gif2swf. | |||||
| CVE-2017-1000176 | 1 Swftools | 1 Swftools | 2026-06-17 | 4.3 MEDIUM | 5.5 MEDIUM |
| In SWFTools, a memcpy buffer overflow was found in swfc. | |||||
| CVE-2017-1000174 | 1 Swftools | 1 Swftools | 2026-06-17 | 4.3 MEDIUM | 5.5 MEDIUM |
| In SWFTools, an address access exception was found in swfdump swf_GetBits(). | |||||
| CVE-2017-1000127 | 1 Exiv2 | 1 Exiv2 | 2026-06-17 | 4.3 MEDIUM | 5.5 MEDIUM |
| Exiv2 0.26 contains a heap buffer overflow in tiff parser | |||||
| CVE-2017-1000118 | 1 Akka | 1 Http Server | 2026-06-17 | 5.0 MEDIUM | 7.5 HIGH |
| Akka HTTP versions <= 10.0.5 Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service | |||||
| CVE-2017-1000101 | 1 Haxx | 1 Curl | 2026-06-17 | 4.3 MEDIUM | 6.5 MEDIUM |
| curl supports "globbing" of URLs, in which a user can pass a numerical range to have the tool iterate over those numbers to do a sequence of transfers. In the globbing function that parses the numerical range, there was an omission that made curl read a byte beyond the end of the URL if given a carefully crafted, or just wrongly written, URL. The URL is stored in a heap based buffer, so it could then be made to wrongly read something else instead of crashing. An example of a URL that triggers the flaw would be `http://ur%20[0-60000000000000000000`. | |||||
| CVE-2017-1000075 | 1 Creolabs | 1 Gravity | 2026-06-17 | 7.5 HIGH | 9.8 CRITICAL |
| Creolabs Gravity version 1.0 is vulnerable to a stack overflow in the memcmp function | |||||