Show filters
490 Total Results
Displaying 211-220 of 490
Sort by:
Attacker Value
Unknown

CVE-2020-4031

Disclosure Date: June 22, 2020 (last updated February 21, 2025)
In FreeRDP before version 2.1.2, there is a use-after-free in gdi_SelectObject. All FreeRDP clients using compatibility mode with /relax-order-checks are affected. This is fixed in version 2.1.2.
Attacker Value
Unknown

CVE-2020-11096

Disclosure Date: June 22, 2020 (last updated February 21, 2025)
In FreeRDP before version 2.1.2, there is a global OOB read in update_read_cache_bitmap_v3_order. As a workaround, one can disable bitmap cache with -bitmap-cache (default). This is fixed in version 2.1.2.
Attacker Value
Unknown

CVE-2020-4032

Disclosure Date: June 22, 2020 (last updated February 21, 2025)
In FreeRDP before version 2.1.2, there is an integer casting vulnerability in update_recv_secondary_order. All clients with +glyph-cache /relax-order-checks are affected. This is fixed in version 2.1.2.
Attacker Value
Unknown

CVE-2020-11097

Disclosure Date: June 22, 2020 (last updated February 21, 2025)
In FreeRDP before version 2.1.2, an out of bounds read occurs resulting in accessing a memory location that is outside of the boundaries of the static array PRIMARY_DRAWING_ORDER_FIELD_BYTES. This is fixed in version 2.1.2.
Attacker Value
Unknown

CVE-2020-11095

Disclosure Date: June 22, 2020 (last updated February 21, 2025)
In FreeRDP before version 2.1.2, an out of bound reads occurs resulting in accessing a memory location that is outside of the boundaries of the static array PRIMARY_DRAWING_ORDER_FIELD_BYTES. This is fixed in version 2.1.2.
Attacker Value
Unknown

CVE-2020-4030

Disclosure Date: June 22, 2020 (last updated February 21, 2025)
In FreeRDP before version 2.1.2, there is an out of bounds read in TrioParse. Logging might bypass string length checks due to an integer overflow. This is fixed in version 2.1.2.
Attacker Value
Unknown

CVE-2020-14954

Disclosure Date: June 21, 2020 (last updated February 21, 2025)
Mutt before 1.14.4 and NeoMutt before 2020-06-19 have a STARTTLS buffering issue that affects IMAP, SMTP, and POP3. When a server sends a "begin TLS" response, the client reads additional data (e.g., from a man-in-the-middle attacker) and evaluates it in a TLS context, aka "response injection."
Attacker Value
Unknown

CVE-2020-3350

Disclosure Date: June 17, 2020 (last updated February 21, 2025)
A vulnerability in the endpoint software of Cisco AMP for Endpoints and Clam AntiVirus could allow an authenticated, local attacker to cause the running software to delete arbitrary files on the system. The vulnerability is due to a race condition that could occur when scanning malicious files. An attacker with local shell access could exploit this vulnerability by executing a script that could trigger the race condition. A successful exploit could allow the attacker to delete arbitrary files on the system that the attacker would not normally have privileges to delete, producing system instability or causing the endpoint software to stop working.
Attacker Value
Unknown

CVE-2020-0198

Disclosure Date: June 11, 2020 (last updated February 21, 2025)
In exif_data_load_data_content of exif-data.c, there is a possible UBSAN abort due to an integer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10Android ID: A-146428941
Attacker Value
Unknown

CVE-2020-8619

Disclosure Date: June 10, 2020 (last updated February 21, 2025)
In ISC BIND9 versions BIND 9.11.14 -> 9.11.19, BIND 9.14.9 -> 9.14.12, BIND 9.16.0 -> 9.16.3, BIND Supported Preview Edition 9.11.14-S1 -> 9.11.19-S1: Unless a nameserver is providing authoritative service for one or more zones and at least one zone contains an empty non-terminal entry containing an asterisk ("*") character, this defect cannot be encountered. A would-be attacker who is allowed to change zone content could theoretically introduce such a record in order to exploit this condition to cause denial of service, though we consider the use of this vector unlikely because any such attack would require a significant privilege level and be easily traceable.