Show filters
116 Total Results
Displaying 11-20 of 116
Sort by:
Attacker Value
Unknown
CVE-2014-8139
Disclosure Date: January 31, 2020 (last updated February 21, 2025)
Heap-based buffer overflow in the CRC32 verification in Info-ZIP UnZip 6.0 and earlier allows remote attackers to execute arbitrary code via a crafted zip file in the -t command argument to the unzip command.
0
Attacker Value
Unknown
CVE-2014-7844
Disclosure Date: January 14, 2020 (last updated February 21, 2025)
BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via a crafted email address.
0
Attacker Value
Unknown
CVE-2019-14823
Disclosure Date: October 14, 2019 (last updated November 27, 2024)
A flaw was found in the "Leaf and Chain" OCSP policy implementation in JSS' CryptoManager versions after 4.4.6, 4.5.3, 4.6.0, where it implicitly trusted the root certificate of a certificate chain. Applications using this policy may not properly verify the chain and could be vulnerable to attacks such as Man in the Middle.
0
Attacker Value
Unknown
CVE-2019-14835
Disclosure Date: September 17, 2019 (last updated December 16, 2023)
A buffer overflow flaw was found, in versions from 2.6.34 to 5.2.x, in the way Linux kernel's vhost functionality that translates virtqueue buffers to IOVs, logged the buffer descriptors during migration. A privileged guest user able to pass descriptors with invalid length to the host when migration is underway, could use this flaw to increase their privileges on the host.
0
Attacker Value
Unknown
CVE-2019-0223
Disclosure Date: April 23, 2019 (last updated November 08, 2023)
While investigating bug PROTON-2014, we discovered that under some circumstances Apache Qpid Proton versions 0.9 to 0.27.0 (C library and its language bindings) can connect to a peer anonymously using TLS *even when configured to verify the peer certificate* while used with OpenSSL versions before 1.1.0. This means that an undetected man in the middle attack could be constructed if an attacker can arrange to intercept TLS traffic.
0
Attacker Value
Unknown
CVE-2017-3139
Disclosure Date: April 09, 2019 (last updated November 27, 2024)
A denial of service flaw was found in the way BIND handled DNSSEC validation. A remote attacker could use this flaw to make named exit unexpectedly with an assertion failure via a specially crafted DNS response.
0
Attacker Value
Unknown
Improper fetch cleanup sequencing in the resolver can cause named to crash
Disclosure Date: January 16, 2019 (last updated November 27, 2024)
BIND was improperly sequencing cleanup operations on upstream recursion fetch contexts, leading in some cases to a use-after-free error that can trigger an assertion failure and crash in named. Affects BIND 9.0.0 to 9.8.x, 9.9.0 to 9.9.11, 9.10.0 to 9.10.6, 9.11.0 to 9.11.2, 9.9.3-S1 to 9.9.11-S1, 9.10.5-S1 to 9.10.6-S1, 9.12.0a1 to 9.12.0rc1.
0
Attacker Value
Unknown
A response packet can cause a resolver to terminate when processing an answer c…
Disclosure Date: January 16, 2019 (last updated November 27, 2024)
Mistaken assumptions about the ordering of records in the answer section of a response containing CNAME or DNAME resource records could lead to a situation in which named would exit with an assertion failure when processing a response in which records occurred in an unusual order. Affects BIND 9.9.9-P6, 9.9.10b1->9.9.10rc1, 9.10.4-P6, 9.10.5b1->9.10.5rc1, 9.11.0-P3, 9.11.1b1->9.11.1rc1, and 9.9.9-S8.
0
Attacker Value
Unknown
CVE-2019-6133
Disclosure Date: January 11, 2019 (last updated November 27, 2024)
In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization decisions are improperly cached. This is related to lack of uid checking in polkitbackend/polkitbackendinteractiveauthority.c.
0
Attacker Value
Unknown
CVE-2018-1000805
Disclosure Date: October 08, 2018 (last updated November 27, 2024)
Paramiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity.
0