Show filters
482 Total Results
Displaying 281-290 of 482
Sort by:
Attacker Value
Unknown
CVE-2017-1000115
Disclosure Date: October 05, 2017 (last updated November 26, 2024)
Mercurial prior to version 4.3 is vulnerable to a missing symlink check that can malicious repositories to modify files outside the repository
0
Attacker Value
Unknown
CVE-2017-1000116
Disclosure Date: October 05, 2017 (last updated November 26, 2024)
Mercurial prior to 4.3 did not adequately sanitize hostnames passed to ssh, leading to possible shell-injection attacks.
0
Attacker Value
Unknown
CVE-2017-1000111
Disclosure Date: October 05, 2017 (last updated November 26, 2024)
Linux kernel: heap out-of-bounds in AF_PACKET sockets. This new issue is analogous to previously disclosed CVE-2016-8655. In both cases, a socket option that changes socket state may race with safety checks in packet_set_ring. Previously with PACKET_VERSION. This time with PACKET_RESERVE. The solution is similar: lock the socket for the update. This issue may be exploitable, we did not investigate further. As this issue affects PF_PACKET sockets, it requires CAP_NET_RAW in the process namespace. But note that with user namespaces enabled, any process can create a namespace in which it has CAP_NET_RAW.
0
Attacker Value
Unknown
CVE-2017-12615
Disclosure Date: September 19, 2017 (last updated July 17, 2024)
When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the readonly initialisation parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.
0
Attacker Value
Unknown
CVE-2017-1000251
Disclosure Date: September 12, 2017 (last updated November 26, 2024)
The native Bluetooth stack in the Linux Kernel (BlueZ), starting at the Linux kernel version 2.6.32 and up to and including 4.13.1, are vulnerable to a stack overflow vulnerability in the processing of L2CAP configuration responses resulting in Remote code execution in kernel space.
0
Attacker Value
Unknown
CVE-2017-0902
Disclosure Date: August 31, 2017 (last updated November 26, 2024)
RubyGems version 2.6.12 and earlier is vulnerable to a DNS hijacking vulnerability that allows a MITM attacker to force the RubyGems client to download and install gems from a server that the attacker controls.
0
Attacker Value
Unknown
CVE-2017-0901
Disclosure Date: August 31, 2017 (last updated November 26, 2024)
RubyGems version 2.6.12 and earlier fails to validate specification names, allowing a maliciously crafted gem to potentially overwrite any file on the filesystem.
0
Attacker Value
Unknown
CVE-2017-0899
Disclosure Date: August 31, 2017 (last updated November 26, 2024)
RubyGems version 2.6.12 and earlier is vulnerable to maliciously crafted gem specifications that include terminal escape characters. Printing the gem specification would execute terminal escape sequences.
0
Attacker Value
Unknown
CVE-2017-0900
Disclosure Date: August 31, 2017 (last updated November 26, 2024)
RubyGems version 2.6.12 and earlier is vulnerable to maliciously crafted gem specifications to cause a denial of service attack against RubyGems clients who have issued a `query` command.
0
Attacker Value
Unknown
CVE-2017-14064
Disclosure Date: August 31, 2017 (last updated November 26, 2024)
Ruby through 2.2.7, 2.3.x through 2.3.4, and 2.4.x through 2.4.1 can expose arbitrary memory during a JSON.generate call. The issues lies in using strdup in ext/json/ext/generator/generator.c, which will stop after encountering a '\0' byte, returning a pointer to a string of length zero, which is not the length stored in space_len.
0