First published: Thu May 05 2011(Updated: )
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] <a href="http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01342.html">http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01342.html</a> [2] <a href="http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01347.html">http://www.mail-archive.com/tigervnc-devel@lists.sourceforge.net/msg01347.html</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
TigerVNC | =1.1-beta1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-1775 is categorized as a moderate severity vulnerability due to potential credential exposure.
To mitigate CVE-2011-1775, users should upgrade to a version of TigerVNC that addresses the certificate validation issue.
CVE-2011-1775 specifically affects TigerVNC version 1.1-beta1 due to improper certificate validation.
The main risk of CVE-2011-1775 is that a malicious server could obtain legitimate client authentication credentials.
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.