Show filters
827 Total Results
Displaying 181-190 of 827
Sort by:
Attacker Value
Unknown

CVE-2020-27824

Disclosure Date: May 13, 2021 (last updated February 22, 2025)
A flaw was found in OpenJPEG’s encoder in the opj_dwt_calc_explicit_stepsizes() function. This flaw allows an attacker who can supply crafted input to decomposition levels to cause a buffer overflow. The highest threat from this vulnerability is to system availability.
Attacker Value
Unknown

CVE-2021-3507

Disclosure Date: May 06, 2021 (last updated February 22, 2025)
A heap buffer overflow was found in the floppy disk emulator of QEMU up to 6.0.0 (including). It could occur in fdctrl_transfer_handler() in hw/block/fdc.c while processing DMA read data transfers from the floppy drive to the guest system. A privileged guest user could use this flaw to crash the QEMU process on the host resulting in DoS scenario, or potential information leakage from the host memory.
Attacker Value
Unknown

CVE-2021-3472

Disclosure Date: April 26, 2021 (last updated February 22, 2025)
A flaw was found in xorg-x11-server in versions before 1.20.11. An integer underflow can occur in xserver which can lead to a local privilege escalation. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Attacker Value
Unknown

CVE-2021-3497

Disclosure Date: April 19, 2021 (last updated February 22, 2025)
GStreamer before 1.18.4 might access already-freed memory in error code paths when demuxing certain malformed Matroska files.
Attacker Value
Unknown

CVE-2021-3498

Disclosure Date: April 19, 2021 (last updated February 22, 2025)
GStreamer before 1.18.4 might cause heap corruption when parsing certain malformed Matroska files.
Attacker Value
Unknown

CVE-2021-3482

Disclosure Date: April 08, 2021 (last updated February 22, 2025)
A flaw was found in Exiv2 in versions before and including 0.27.4-RC1. Improper input validation of the rawData.size property in Jp2Image::readMetadata() in jp2image.cpp can lead to a heap-based buffer overflow via a crafted JPG image containing malicious EXIF data.
Attacker Value
Unknown

CVE-2021-20305

Disclosure Date: April 05, 2021 (last updated February 22, 2025)
A flaw was found in Nettle in versions before 3.7.2, where several Nettle signature verification functions (GOST DSA, EDDSA & ECDSA) result in the Elliptic Curve Cryptography point (ECC) multiply function being called with out-of-range scalers, possibly resulting in incorrect results. This flaw allows an attacker to force an invalid signature, causing an assertion failure or possible validation. The highest threat to this vulnerability is to confidentiality, integrity, as well as system availability.
Attacker Value
Unknown

CVE-2021-20270

Disclosure Date: March 23, 2021 (last updated February 22, 2025)
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.
Attacker Value
Unknown

CVE-2021-21349

Disclosure Date: March 23, 2021 (last updated February 22, 2025)
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
Attacker Value
Unknown

CVE-2021-21346

Disclosure Date: March 23, 2021 (last updated February 22, 2025)
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.