Show filters
118 Total Results
Displaying 31-40 of 118
Sort by:
Attacker Value
Unknown

CVE-2019-20788

Disclosure Date: April 23, 2020 (last updated February 21, 2025)
libvncclient/cursor.c in LibVNCServer through 0.9.12 has a HandleCursorShape integer overflow and heap-based buffer overflow via a large height or width value. NOTE: this may overlap CVE-2019-15690.
Attacker Value
Unknown

CVE-2010-5304

Disclosure Date: February 05, 2020 (last updated February 21, 2025)
A NULL pointer dereference flaw was found in the way LibVNCServer before 0.9.9 handled certain ClientCutText message. A remote attacker could use this flaw to crash the VNC server by sending a specially crafted ClientCutText message from a VNC client.
Attacker Value
Unknown

CVE-2014-0011

Disclosure Date: January 02, 2020 (last updated February 21, 2025)
Multiple heap-based buffer overflows in the ZRLE_DECODE function in common/rfb/zrleDecode.h in TigerVNC before 1.3.1, when NDEBUG is enabled, allow remote VNC servers to cause a denial of service (vncviewer crash) and possibly execute arbitrary code via vectors related to screen image rendering.
Attacker Value
Unknown

CVE-2019-15692

Disclosure Date: December 26, 2019 (last updated November 27, 2024)
TigerVNC version prior to 1.10.1 is vulnerable to heap buffer overflow. Vulnerability could be triggered from CopyRectDecoder due to incorrect value checks. Exploitation of this vulnerability could potentially result into remote code execution. This attack appear to be exploitable via network connectivity.
Attacker Value
Unknown

CVE-2019-15693

Disclosure Date: December 26, 2019 (last updated November 27, 2024)
TigerVNC version prior to 1.10.1 is vulnerable to heap buffer overflow, which occurs in TightDecoder::FilterGradient. Exploitation of this vulnerability could potentially result into remote code execution. This attack appear to be exploitable via network connectivity.
Attacker Value
Unknown

CVE-2019-15694

Disclosure Date: December 26, 2019 (last updated November 27, 2024)
TigerVNC version prior to 1.10.1 is vulnerable to heap buffer overflow, which could be triggered from DecodeManager::decodeRect. Vulnerability occurs due to the signdness error in processing MemOutStream. Exploitation of this vulnerability could potentially result into remote code execution. This attack appear to be exploitable via network connectivity.
Attacker Value
Unknown

CVE-2019-15691

Disclosure Date: December 26, 2019 (last updated November 27, 2024)
TigerVNC version prior to 1.10.1 is vulnerable to stack use-after-return, which occurs due to incorrect usage of stack memory in ZRLEDecoder. If decoding routine would throw an exception, ZRLEDecoder may try to access stack variable, which has been already freed during the process of stack unwinding. Exploitation of this vulnerability could potentially result into remote code execution. This attack appear to be exploitable via network connectivity.
Attacker Value
Unknown

CVE-2019-15683

Disclosure Date: October 29, 2019 (last updated November 27, 2024)
TurboVNC server code contains stack buffer overflow vulnerability in commit prior to cea98166008301e614e0d36776bf9435a536136e. This could possibly result into remote code execution, since stack frame is not protected with stack canary. This attack appear to be exploitable via network connectivity. To exploit this vulnerability authorization on server is required. These issues have been fixed in commit cea98166008301e614e0d36776bf9435a536136e.
Attacker Value
Unknown

CVE-2019-8287

Disclosure Date: October 29, 2019 (last updated November 27, 2024)
TightVNC code version 1.3.10 contains global buffer overflow in HandleCoRREBBP macro function, which can potentially result code execution. This attack appear to be exploitable via network connectivity.
Attacker Value
Unknown

CVE-2019-15679

Disclosure Date: October 29, 2019 (last updated November 27, 2024)
TightVNC code version 1.3.10 contains heap buffer overflow in InitialiseRFBConnection function, which can potentially result code execution. This attack appear to be exploitable via network connectivity.