CVE-2009-2666
UnknownEPSS 1.50%
Last modified
CVE-2009-2666 is a vulnerability of currently unknown severity. socket.c in fetchmail before 6.3.11 does not properly handle a '\0' character in a domain name in the subject's Common Name (CN) 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.. EPSS estimates a 1.50% chance of exploitation in the next 30 days.
Description
socket.c in fetchmail before 6.3.11 does not properly handle a '\0' character in a domain name in the subject's Common Name (CN) 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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Fetchmail | Fetchmail | <= 6.3.10 | — |
| Fetchmail | Fetchmail | 4.5.1 | — |
| Fetchmail | Fetchmail | 4.5.2 | — |
| Fetchmail | Fetchmail | 4.5.3 | — |
| Fetchmail | Fetchmail | 4.5.4 | — |
| Fetchmail | Fetchmail | 4.5.5 | — |
| Fetchmail | Fetchmail | 4.5.6 | — |
| Fetchmail | Fetchmail | 4.5.7 | — |
| Fetchmail | Fetchmail | 4.5.8 | — |
| Fetchmail | Fetchmail | 4.6.0 | — |
| Fetchmail | Fetchmail | 4.6.1 | — |
| Fetchmail | Fetchmail | 4.6.2 | — |
| Fetchmail | Fetchmail | 4.6.3 | — |
| Fetchmail | Fetchmail | 4.6.4 | — |
| Fetchmail | Fetchmail | 4.6.5 | — |
| Fetchmail | Fetchmail | 4.6.6 | — |
| Fetchmail | Fetchmail | 4.6.7 | — |
| Fetchmail | Fetchmail | 4.6.8 | — |
| Fetchmail | Fetchmail | 4.6.9 | — |
| Fetchmail | Fetchmail | 4.7.0 | — |
| Fetchmail | Fetchmail | 4.7.1 | — |
| Fetchmail | Fetchmail | 4.7.2 | — |
| Fetchmail | Fetchmail | 4.7.3 | — |
| Fetchmail | Fetchmail | 4.7.4 | — |
| Fetchmail | Fetchmail | 4.7.5 | — |
| Fetchmail | Fetchmail | 4.7.6 | — |
| Fetchmail | Fetchmail | 4.7.7 | — |
| Fetchmail | Fetchmail | 5.0.0 | — |
| Fetchmail | Fetchmail | 5.0.1 | — |
| Fetchmail | Fetchmail | 5.0.2 | — |
| Fetchmail | Fetchmail | 5.0.3 | — |
| Fetchmail | Fetchmail | 5.0.4 | — |
| Fetchmail | Fetchmail | 5.0.5 | — |
| Fetchmail | Fetchmail | 5.0.6 | — |
| Fetchmail | Fetchmail | 5.0.7 | — |
| Fetchmail | Fetchmail | 5.0.8 | — |
| Fetchmail | Fetchmail | 5.1.0 | — |
| Fetchmail | Fetchmail | 5.1.4 | — |
| Fetchmail | Fetchmail | 5.2.0 | — |
| Fetchmail | Fetchmail | 5.2.1 | — |
| Fetchmail | Fetchmail | 5.2.3 | — |
| Fetchmail | Fetchmail | 5.2.4 | — |
| Fetchmail | Fetchmail | 5.2.7 | — |
| Fetchmail | Fetchmail | 5.2.8 | — |
| Fetchmail | Fetchmail | 5.3.0 | — |
| Fetchmail | Fetchmail | 5.3.1 | — |
| Fetchmail | Fetchmail | 5.3.3 | — |
| Fetchmail | Fetchmail | 5.3.8 | — |
| Fetchmail | Fetchmail | 5.4.0 | — |
| Fetchmail | Fetchmail | 5.4.3 | — |
Showing 50 of 103 affected configurations. See NVD for the full list.
References
- https://secunia.com/advisories/36175Vendor Advisory
- https://secunia.com/advisories/36179Vendor Advisory
- https://secunia.com/advisories/36236Vendor Advisory
- https://www.vupen.com/english/advisories/2009/2155Vendor Advisory
- https://www.vupen.com/english/advisories/2009/3184Vendor Advisory
- https://secunia.com/advisories/36175Vendor Advisory
- https://secunia.com/advisories/36179Vendor Advisory
- https://secunia.com/advisories/36236Vendor Advisory
- https://www.vupen.com/english/advisories/2009/2155Vendor Advisory
- https://www.vupen.com/english/advisories/2009/3184Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2009-2666?
socket.c in fetchmail before 6.3.11 does not properly handle a '\0' character in a domain name in the subject's Common Name (CN) 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.
How severe is CVE-2009-2666?
Severity scoring for CVE-2009-2666 is pending analysis. The EPSS model estimates a 1.50% probability of exploitation in the next 30 days.
How do I fix CVE-2009-2666?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2009
- CVE-2009-2660Multiple integer overflows in CamlImages 2.2 might allow con…
- CVE-2009-2661The asn1_length function in strongSwan 2.8 before 2.8.11, 4.…
- CVE-2009-2662The browser engine in Mozilla Firefox 3.5.x before 3.5.2 all…
- CVE-2009-2663libvorbis before r16182, as used in Mozilla Firefox 3.5.x be…
- CVE-2009-2664The js_watch_set function in js/src/jsdbgapi.cpp in the Java…
- CVE-2009-2665The nsDocument::SetScriptGlobalObject function in content/ba…
- CVE-2009-2667Unspecified vulnerability in IBM Tivoli Key Lifecycle Manage…
- CVE-2009-2668Microsoft Internet Explorer 6 through 6.0.2900.2180 and 7 th…
- CVE-2009-2669A certain debugging component in IBM AIX 5.3 and 6.1 does no…
- CVE-2009-2670The audio system in Sun Java Runtime Environment (JRE) in JD…
- CVE-2009-2671The SOCKS proxy implementation in Sun Java Runtime Environme…
- CVE-2009-2672The proxy mechanism implementation in Sun Java Runtime Envir…
Are you affected by CVE-2009-2666?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST