CVE-2005-0021: Buffer Overflow
First published: Mon May 02 2005(Updated: )
Multiple buffer overflows in Exim before 4.43 may allow attackers to execute arbitrary code via (1) an IPv6 address with more than 8 components, as demonstrated using the -be command line option, which triggers an overflow in the host_aton function, or (2) the -bh command line option or dnsdb PTR lookup, which triggers an overflow in the dns_build_reverse function.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Exim | <=4.40 | |
| Exim | =4.41 | |
| Exim | =4.42 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.idefense.com/application/poi/display?id=179&type=vulnerabilities
- http://www.idefense.com/application/poi/display?id=183&type=vulnerabilities
- http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20050103/msg00028.html
- http://ftp6.us.freebsd.org/pub/mail/exim/ChangeLogs/ChangeLog-4.44
- http://www.debian.org/security/2005/dsa-635
- http://www.debian.org/security/2005/dsa-637
- http://security.gentoo.org/glsa/glsa-200501-23.xml
- http://www.redhat.com/support/errata/RHSA-2005-025.html
- http://www.kb.cert.org/vuls/id/132992
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10347
Frequently Asked Questions
What is the severity of CVE-2005-0021?
CVE-2005-0021 is classified as a critical vulnerability due to the potential for remote code execution.
How do I fix CVE-2005-0021?
To fix CVE-2005-0021, upgrade Exim to version 4.43 or later, as this version addresses the buffer overflow vulnerabilities.
What versions of Exim are affected by CVE-2005-0021?
CVE-2005-0021 affects Exim versions prior to 4.43, specifically 4.40 and any version between 4.41 and 4.42.
What can an attacker do with CVE-2005-0021?
An attacker can exploit CVE-2005-0021 to execute arbitrary code on the vulnerable Exim server.
Is there a workaround for CVE-2005-0021?
As of the information available, the best course of action is to update Exim to a patched version since no effective workaround is recommended.
- agent/references
- agent/type
- agent/last-modified-date
- agent/remedy
- agent/first-publish-date
- agent/severity
- agent/description
- agent/weakness
- agent/author
- agent/tags
- agent/softwarecombine
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/university of cambridge
- vendor/exim
- canonical/exim
- version/exim/4.40
- version/exim/4.41
- version/exim/4.42