Vulnerabilities · 2011 · Dovecot
CVE-2011-4318
Dovecot vulnerability
Dovecot 2.0.x before 2.0.16, when ssl or starttls is enabled and hostname is used to define the proxy destination, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a valid certificate for a different hostname.
Affected products
Dovecot. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Dovecot 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
- rhn.redhat.com/errata/RHSA-2013-0520.html · Vendor Advisory
- secunia.com/advisories/52311 · Vendor Advisory
- hg.dovecot.org/dovecot-2.0/rev/5e9eaf63a6b1
- secunia.com/advisories/46886
- www.dovecot.org/list/dovecot-news/2011-November/000200.html
- www.openwall.com/lists/oss-security/2011/11/18/5
- www.openwall.com/lists/oss-security/2011/11/18/7
- bugs.gentoo.org/show_bug.cgi?id=390887
- nvd.nist.gov/vuln/detail/CVE-2011-4318
- cve.org/CVERecord?id=CVE-2011-4318
More vulnerabilities in Dovecot products
CVE-2022-30550CVE-2021-33515CVE-2021-29157CVE-2020-28200CVE-2020-25275CVE-2020-24386CVE-2020-12674CVE-2020-12673All 53
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.