CVE-2020-29260

libvncclient v0.9.13 was discovered to contain a memory leak via the function rfbClientCleanup().

Published: 2022-09-02 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-29260 is rated Moderate Risk (57.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.94%). Review affected assets and schedule 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-2020-29260

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-05-28 0.16% 0.94% +0.78%
2 2025-12-18 0.14% 0.16% +0.03%
3 2025-11-21 — 0.14% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-29260

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2020-29260

OS Trackers for CVE-2020-29260

vendor priority summary link
alpine high CVE-2020-29260: 1 source package rows (libvncserver); 10 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 8, open 2. https://security.alpinelinux.org/vuln/CVE-2020-29260
debian not yet assigned CVE-2020-29260 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-2020-29260
redhat medium — https://access.redhat.com/security/cve/CVE-2020-29260
suse medium — https://www.suse.com/security/cve/CVE-2020-29260/
ubuntu low CVE-2020-29260 low priority: Ubuntu including 6 source packages (italc, libvncserver, tightvnc, veyon, vino, x11vnc), 71 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 32, ignored 25, not-affected 11, DNE 3. https://ubuntu.com/security/CVE-2020-29260

Affected software / configurations for CVE-2020-29260

Vendor Product Version Raw CPE
libvncserver_project libvncserver 0.9.13 cpe:2.3:a:libvncserver_project:libvncserver:0.9.13:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2020-29260

cvelogic Threat Intelligence