CVE-2011-1775: Input Validation
It was reported [1] that vncviewer could prompt for, and send, authentication credentials to a remote server without first properly validating the X.509 certificate. This could allow a malicious server to obtain a client's credentials because the client does not indicate to the user that a certificate is bad or missing.
A proposed patch [2] is being discussed.
[1] http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01342.html [2] http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01347.html
Other sources
The CSecurityTLS::processMsg function in common/rfb/CSecurityTLS.cxx in the vncviewer component in TigerVNC 1.1beta1 does not properly verify the server's X.509 certificate, which allows man-in-the-middle attackers to spoof a TLS VNC server via an arbitrary certificate.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2011-1775?
CVE-2011-1775 is categorized as a moderate severity vulnerability due to potential credential exposure.
How do I fix CVE-2011-1775?
To mitigate CVE-2011-1775, users should upgrade to a version of TigerVNC that addresses the certificate validation issue.
What does CVE-2011-1775 affect?
CVE-2011-1775 specifically affects TigerVNC version 1.1-beta1 due to improper certificate validation.
What is the main risk associated with CVE-2011-1775?
The main risk of CVE-2011-1775 is that a malicious server could obtain legitimate client authentication credentials.
Is CVE-2011-1775 still a risk today?
While CVE-2011-1775 may be less prevalent due to older software being outdated, it still poses a risk for legacy systems using vulnerable versions.