First published: Wed Nov 28 2012(Updated: )
A Debian bug report [1] indicated that Links does not properly verify SSL certificates. If you visit a web site with an expired SSL certificate, Links will only display "SSL error" without any indication as to what the error was. This, in and of itself, is not a flaw however when testing, I found that when you go to a site with a valid SSL certificate, but for a different hostname (for example, if you go to <a href="https://alias.foo.com">https://alias.foo.com</a> which might be a CNAME or a proxy for <a href="https://foo.com">https://foo.com</a>) Links will connect without any errors or warnings. Doing the same in a browser like Google Chrome, however, reports "You attempted to reach alias.foo.com, but instead you actually reached a server identifying itself as foo.com." and allows you to either proceed or not, before loading the site. [1] <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694658">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694658</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
WP Links Page | =0.12 | |
twibright labs Links | =2.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-6709 has a moderate severity level due to improper SSL certificate verification.
CVE-2012-6709 can lead users to unknowingly accept expired SSL certificates without proper warnings.
CVE-2012-6709 affects Links versions 2.3 and ELinks version 0.12.
As of now, there are no known public exploits specifically targeting CVE-2012-6709.
To mitigate CVE-2012-6709, users should upgrade to a version of Links or ELinks that addresses SSL verification issues.