| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Paul L Daniels ripMIME 1.3.1.0. It has been classified as problematic. Affected by this issue is the function mimeh_read_headers. This manipulation causes an unknown weakness.
This vulnerability is tracked as CVE-2004-2620. No exploit exists.
Details
A vulnerability was found in Paul L Daniels ripMIME 1.3.1.0. It has been declared as problematic. As an impact it is known to affect integrity. The summary by CVE is:
The MIMEH_read_headers function in ripMIME 1.3.1.0 does not properly handle trailing "\r" and "\n" characters in headers, which leads to a buffer underflow.
The weakness was disclosed 04/05/2004 (Website). The advisory is shared at osvdb.org. This vulnerability is known as CVE-2004-2620 since 12/04/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at OSVDB (8731†). The entry VDB-23496 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: UnknownCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
04/05/2004 🔍08/14/2004 🔍
12/31/2004 🔍
12/04/2005 🔍
03/09/2015 🔍
06/30/2018 🔍
Sources
Advisory: osvdb.org⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2004-2620 (🔍)
GCVE (CVE): GCVE-0-2004-2620
GCVE (VulDB): GCVE-100-23497
OSVDB: 8731 - ripMIME MIMEH_read_headers() underrun
See also: 🔍
Entry
Created: 03/09/2015 16:55Updated: 06/30/2018 09:12
Changes: 03/09/2015 16:55 (43), 06/30/2018 09:12 (6)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.