Hastymail up to 1.5 SMTP Server crlf.crlf smtp_message input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Hastymail 1.0.1/1.0.2/1.1/1.2/1.5. This affects an unknown part of the file crlf.crlf of the component SMTP Server. The manipulation of the argument smtp_message leads to input validation. This vulnerability is documented as CVE-2006-5313. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in Hastymail 1.0.1/1.0.2/1.1/1.2/1.5. This issue affects an unknown code of the file crlf.crlf of the component SMTP Server. The manipulation of the argument smtp_message with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Hastymail 1.5 and earlier before 20061008 allows remote authenticated users to send arbitrary SMTP commands by placing them after a CRLF.CRLF sequence in the smtp_message parameter. NOTE: this crosses privilege boundaries if the SMTP server configuration prevents a user from establishing a direct SMTP session. NOTE: this is a different type of issue than CVE-2006-5262.
The weakness was released 10/17/2006 by Vicente Aguilera Diaz (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2006-5313 since 10/17/2006. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
It is declared as proof-of-concept.
The vulnerability is also documented in the databases at X-Force (29407), SecurityFocus (BID 20424†) and Secunia (SA22308†). Entries connected to this vulnerability are available at VDB-23571 and VDB-32734. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.5
VulDB Base Score: 6.3
VulDB Temp Score: 5.5
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/10/2006 🔍10/17/2006 🔍
10/17/2006 🔍
10/17/2006 🔍
03/12/2015 🔍
04/24/2026 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Vicente Aguilera Diaz
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-5313 (🔍)
GCVE (CVE): GCVE-0-2006-5313
GCVE (VulDB): GCVE-100-32771
X-Force: 29407 - Hastymail IMAP and SMTP server command execution
SecurityFocus: 20424 - Hastymail IMAP SMTP Command Injection Vulnerability
Secunia: 22308
Vupen: ADV-2006-3956
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 04/24/2026 12:41
Changes: 03/12/2015 22:21 (50), 08/06/2018 07:24 (9), 04/24/2026 12:41 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.