Show filters
15 Total Results
Displaying 11-15 of 15
Sort by:
Attacker Value
Unknown
CVE-2021-20270
Disclosure Date: March 23, 2021 (last updated November 28, 2024)
An infinite loop in SMLLexer in Pygments versions 1.5 to 2.7.3 may lead to denial of service when performing syntax highlighting of a Standard ML (SML) source file, as demonstrated by input that only contains the "exception" keyword.
0
Attacker Value
Unknown
CVE-2020-14365
Disclosure Date: September 23, 2020 (last updated February 22, 2025)
A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.
0
Attacker Value
Unknown
CVE-2015-5694
Disclosure Date: November 22, 2019 (last updated November 27, 2024)
Designate does not enforce the DNS protocol limit concerning record set sizes
0
Attacker Value
Unknown
CVE-2019-9515
Disclosure Date: August 13, 2019 (last updated January 15, 2025)
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
0
Attacker Value
Unknown
CVE-2019-9514
Disclosure Date: August 13, 2019 (last updated January 15, 2025)
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.
0