CVE-2002-1175
Last modified
CVE-2002-1175 is a vulnerability of currently unknown severity. The getmxrecord function in Fetchmail 6.0.0 and earlier does not properly check the boundary of a particular malformed DNS packet from a malicious DNS server, which allows remote attackers to cause a denial of service (crash) when Fetchmail attempts to read data beyond the expected boundary.. EPSS estimates a 1.99% chance of exploitation in the next 30 days.
Description
The getmxrecord function in Fetchmail 6.0.0 and earlier does not properly check the boundary of a particular malformed DNS packet from a malicious DNS server, which allows remote attackers to cause a denial of service (crash) when Fetchmail attempts to read data beyond the expected boundary.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Fetchmail | Fetchmail | <= 6.0.0 |
| 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 79 affected configurations. See NVD for the full list.
References
- http://www.iss.net/security_center/static/10203.phpVendor Advisory
- http://www.linux-mandrake.com/en/security/2002/MDKSA-2002-063.phpPatch, Vendor Advisory
- http://www.iss.net/security_center/static/10203.phpVendor Advisory
- http://www.linux-mandrake.com/en/security/2002/MDKSA-2002-063.phpPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2002-1175?
How severe is CVE-2002-1175?
How do I fix CVE-2002-1175?
Are you affected by CVE-2002-1175?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
