Export limit exceeded: 14342 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (14342 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2017-8387 | 1 Stdutility | 1 Stdu Viewer | 2025-04-20 | N/A |
| STDU Viewer version 1.6.375 might allow user-assisted attackers to execute code via a crafted file. One threat model is a victim who obtains an untrusted crafted file from a remote location and issues several user-defined commands including Ctrl-+ commands. | ||||
| CVE-2017-0761 | 1 Google | 1 Android | 2025-04-20 | N/A |
| A remote code execution vulnerability in the Android media framework (libavc). Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID: A-38448381. | ||||
| CVE-2017-0781 | 1 Google | 1 Android | 2025-04-20 | N/A |
| A remote code execution vulnerability in the Android system (bluetooth). Product: Android. Versions: 4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0. Android ID: A-63146105. | ||||
| CVE-2017-1000118 | 1 Akka | 1 Http Server | 2025-04-20 | N/A |
| Akka HTTP versions <= 10.0.5 Illegal Media Range in Accept Header Causes StackOverflowError Leading to Denial of Service | ||||
| CVE-2017-1000127 | 1 Exiv2 | 1 Exiv2 | 2025-04-20 | N/A |
| Exiv2 0.26 contains a heap buffer overflow in tiff parser | ||||
| CVE-2017-1000174 | 1 Swftools | 1 Swftools | 2025-04-20 | N/A |
| In SWFTools, an address access exception was found in swfdump swf_GetBits(). | ||||
| CVE-2017-1000176 | 1 Swftools | 1 Swftools | 2025-04-20 | N/A |
| In SWFTools, a memcpy buffer overflow was found in swfc. | ||||
| CVE-2017-1000185 | 1 Swftools | 1 Swftools | 2025-04-20 | N/A |
| In SWFTools, a memcpy buffer overflow was found in gif2swf. | ||||
| CVE-2017-1000186 | 1 Swftools | 1 Swftools | 2025-04-20 | N/A |
| In SWFTools, a stack overflow was found in pdf2swf. | ||||
| CVE-2017-1000187 | 1 Swftools | 1 Swftools | 2025-04-20 | N/A |
| In SWFTools, an address access exception was found in pdf2swf. FoFiTrueType::writeTTF() | ||||
| CVE-2017-1000198 | 2 Redhat, Tcmu-runner Project | 2 Storage, Tcmu-runner | 2025-04-20 | N/A |
| 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-1000206 | 1 Htslib | 1 Htslib | 2025-04-20 | N/A |
| 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-1000210 | 1 Altran | 1 Picotcp | 2025-04-20 | N/A |
| 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-1000231 | 1 Nlnetlabs | 1 Ldns | 2025-04-20 | N/A |
| A double-free vulnerability in parse.c in ldns 1.7.0 have unspecified impact and attack vectors. | ||||
| CVE-2017-1000232 | 1 Nlnetlabs | 1 Ldns | 2025-04-20 | N/A |
| A double-free vulnerability in str2host.c in ldns 1.7.0 have unspecified impact and attack vectors. | ||||
| CVE-2017-1000249 | 1 File Project | 1 File | 2025-04-20 | N/A |
| 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-1000254 | 2 Haxx, Redhat | 3 Libcurl, Jboss Core Services, Rhel Software Collections | 2025-04-20 | N/A |
| 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-1000364 | 2 Linux, Redhat | 10 Linux Kernel, Container Development Kit, Enterprise Linux and 7 more | 2025-04-20 | N/A |
| 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-1000366 | 8 Debian, Gnu, Mcafee and 5 more | 26 Debian Linux, Glibc, Web Gateway and 23 more | 2025-04-20 | N/A |
| 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-1000375 | 1 Netbsd | 1 Netbsd | 2025-04-20 | N/A |
| 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. | ||||