CVE-2019-15690

LibVNCServer 0.9.12 release and earlier contains heap buffer overflow vulnerability within the HandleCursorShape() function in libvncclient/cursor.c. An attacker sends cursor shapes with specially crafted dimensions, which can result in remote code execution.

Published: 2025-01-24 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-15690 is rated High Risk (68.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 4.33%). EPSS rose +2.67% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-15690

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-04 1.66% 4.33% +2.67%
2 2025-11-21 0.86% 1.66% +0.80%
3 2025-11-18 — 0.86% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-15690

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2019-15690

OS Trackers for CVE-2019-15690

vendor priority summary link
alpine high CVE-2019-15690: 1 source package rows (libvncserver); 6 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 6. https://security.alpinelinux.org/vuln/CVE-2019-15690
debian not yet assigned CVE-2019-15690 not yet assigned priority: Debian including 1 source packages (libvncserver), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-15690
redhat high — https://access.redhat.com/security/cve/CVE-2019-15690
suse high CVE-2019-15690 severity important: SUSE including 23 source package names (LibVNCServer-0.9.1-160.14.1, LibVNCServer-devel-0.9.10-4.14.1, …), 88 product×package rows across 52 product lines (HPE Helion OpenStack 8, SUSE Enterprise Storage 5, … (52 product lines)): Fixed 88. https://www.suse.com/security/cve/CVE-2019-15690/
ubuntu medium CVE-2019-15690 medium priority: Ubuntu including 2 source packages (libvncserver, x11vnc), 34 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 20, ignored 7, released 4, needs-triage 2, DNE 1. https://ubuntu.com/security/CVE-2019-15690

Affected software / configurations for CVE-2019-15690

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2019-15690

cvelogic Threat Intelligence