CVE-2010-2074
W3m vulnerability
istream.c in w3m 0.5.2 and possibly other versions, when ssl_verify_server is enabled, does not properly handle a '\0' character in a domain name in the (1) subject's Common Name or (2) Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority, a related issue to CVE-2009-2408.
Affected products
W3m. The exact versions are in the references.
What to do now
- Check your exposureFind out whether W3m runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- secunia.com/advisories/40134 · Vendor Advisory
- www.vupen.com/english/advisories/2010/1467 · Vendor Advisory
- lists.fedoraproject.org/pipermail/package-announce/2010-July/044401.html
- lists.opensuse.org/opensuse-security-announce/2010-08/msg00001.html
- osvdb.org/65538
- secunia.com/advisories/40733
- www.openwall.com/lists/oss-security/2010/06/14/4
- www.redhat.com/support/errata/RHSA-2010-0565.html
- nvd.nist.gov/vuln/detail/CVE-2010-2074
- cve.org/CVERecord?id=CVE-2010-2074
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.