Exim Internet Mailer up to 4.43 IPv6 Address host_aton long IPv6 Address memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Exim Internet Mailer up to 4.43. This issue affects the function host_aton of the component IPv6 Address Handler. This manipulation as part of long IPv6 Address causes memory corruption.
This vulnerability appears as CVE-2005-0022. The attack may be initiated remotely. In addition, an exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability has been found in Exim Internet Mailer up to 4.43 (Mail Server Software) and classified as problematic. Affected by this vulnerability is the function host_aton of the component IPv6 Address Handler. The manipulation as part of a long IPv6 Address leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in the spa_base64_to_bits function in Exim before 4.43, as originally obtained from Samba code, and as called by the auth_spa_client function, may allow attackers to execute arbitrary code during SPA authentication.
The bug was discovered 01/04/2005. The weakness was presented 01/06/2005 by Philip Hazel with Exim Team (Website). The advisory is shared at exim.org. This vulnerability is known as CVE-2005-0022 since 01/04/2005. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
A public exploit has been developed in ANSI C and been published 2 months after the advisory. It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 16111 (Exim < 4.44 Multiple Overflows), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SMTP problems and running in the context r.
Upgrading to version 4.44 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at exim.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published 6 days after the disclosure of the vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 4210.
The vulnerability is also documented in the databases at X-Force (18764), Tenable (16111), SecurityFocus (BID 12188†), OSVDB (12727†) and Secunia (SA13713†). See VDB-1094 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 4.0
- 4.1
- 4.2
- 4.3
- 4.4
- 4.5
- 4.6
- 4.7
- 4.8
- 4.9
- 4.10
- 4.11
- 4.12
- 4.13
- 4.14
- 4.15
- 4.16
- 4.17
- 4.18
- 4.19
- 4.20
- 4.21
- 4.22
- 4.23
- 4.24
- 4.25
- 4.26
- 4.27
- 4.28
- 4.29
- 4.30
- 4.31
- 4.32
- 4.33
- 4.34
- 4.35
- 4.36
- 4.37
- 4.38
- 4.39
- 4.40
- 4.41
- 4.42
- 4.43
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.6
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 16111
Nessus Name: Exim < 4.44 Multiple Overflows
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 52252
OpenVAS Name: exim -- two buffer overflow vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍
Upgrade: Internet Mailer 4.44
Patch: exim.org
TippingPoint: 🔍
SourceFire IPS: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍
Timeline
01/04/2005 🔍01/04/2005 🔍
01/04/2005 🔍
01/05/2005 🔍
01/06/2005 🔍
01/06/2005 🔍
01/06/2005 🔍
01/06/2005 🔍
01/07/2005 🔍
01/09/2005 🔍
01/10/2005 🔍
01/12/2005 🔍
02/12/2005 🔍
05/02/2005 🔍
06/30/2019 🔍
Sources
Advisory: exim.orgResearcher: Philip Hazel
Organization: Exim Team
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2005-0022 (🔍)
GCVE (CVE): GCVE-0-2005-0022
GCVE (VulDB): GCVE-100-1093
OVAL: 🔍
X-Force: 18764
SecurityFocus: 12188 - Exim SPA Authentication Remote Buffer Overflow Vulnerability
Secunia: 13713 - Exim Three Vulnerabilities, Moderately Critical
OSVDB: 12727 - Exim SPA Authentication spa_base64_to_bits Function Remote Overflow
SecurityTracker: 1012771
Vulnerability Center: 6812 - Buffer Overflow in University of Cambridge Exim <= 4.43 via SPA Authentication, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 01/10/2005 12:19Updated: 06/30/2019 20:18
Changes: 01/10/2005 12:19 (110), 06/30/2019 20:18 (2)
Complete: 🔍
Cache ID: 216:29D:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.