VYPR
Unrated severityNVD Advisory· Published Sep 2, 2022· Updated Aug 4, 2024

CVE-2020-29260

CVE-2020-29260

Description

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

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

libvncclient v0.9.13 has a memory leak in rfbClientCleanup() that can be triggered by repeated connections.

Vulnerability

libvncclient v0.9.13, part of LibVNCServer, contains a memory leak in the rfbClientCleanup() function. The function fails to free the vncRec structure allocated for each client connection, resulting in memory not being released when a client disconnects. This affects all applications using libvncclient v0.9.13.

Exploitation

An attacker can repeatedly connect to a server using a vulnerable libvncclient-based client, causing multiple allocations of the vncRec structure that are never freed. No special privileges are required beyond the ability to initiate VNC connections.

Impact

Repeatedly triggering the memory leak can exhaust available memory on the system running the vulnerable client, potentially causing denial of service (DoS) due to resource exhaustion. The leak does not lead to code execution or information disclosure.

Mitigation

The fix was committed in commit bef41f6 [1] to the LibVNCServer repository, which adds the missing free(vncRec) call in rfbClientCleanup(). Users should update to a version containing this fix or apply the patch. No workaround is available.

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

11

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

2

News mentions

0

No linked articles in our index yet.