Information disclosure in LibVNC
| Risk | Medium |
| Patch available | YES |
| Number of vulnerabilities | 1 |
| CVE-ID | CVE-2019-15681 |
| CWE-ID | CWE-401 |
| Exploitation vector | Network |
| Public exploit | N/A |
| Vulnerable software Subscribe |
LibVNCServer Server applications / Remote management servers, RDP, SSH |
| Vendor | LibVNC |
Security Bulletin
This security bulletin contains information about 1 vulnerabilities.
Updated: 30.06.2020
Updated list of affected and fixed versions, changed bulletin status to patched.
1) Memory leak
EUVDB-ID: #VU22957
Risk: Medium
CVSSv3.1: 6.9 [CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:U/RC:C]
CVE-ID: CVE-2019-15681
CWE-ID:
CWE-401 - Missing release of memory after effective lifetime
Exploit availability: No
DescriptionThe vulnerability allows a remote attacker to gain access to sensitive information on the target system.
The vulnerability exists due memory leak in VNC server code. A remote attacker can read stack memory and disclose sensitive information.
Combined with another vulnerability, it can be used to leak stack memory and bypass ASLR.
MitigationInstall update from vendor's website.
Vulnerable software versionsLibVNCServer: 0.9.0 - 0.9.12
External linkshttp://github.com/LibVNC/libvncserver/commit/d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a
http://ics-cert.kaspersky.com/reports/2019/11/22/vnc-vulnerability-research/
http://lists.debian.org/debian-lts-announce/2019/10/msg00039.html
http://lists.debian.org/debian-lts-announce/2019/10/msg00042.html
Q & A
Can this vulnerability be exploited remotely?
Yes. This vulnerability can be exploited by a remote non-authenticated attacker via the Internet.
How the attacker can exploit this vulnerability?
The attacker would have to send a specially crafted request to the affected application in order to exploit this vulnerability.
Is there known malware, which exploits this vulnerability?
No. We are not aware of malware exploiting this vulnerability.
