| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Perl 2.19. It has been classified as problematic. The affected element is an unknown function. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2004-2591. There is no exploit available.
Details
A vulnerability was found in Perl 2.19 (Programming Language Software). It has been classified as problematic. This affects an unknown code block. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
the data-overwrite capability of buttuglysoftware cleancache 2.19 does not properly overwrite data in files which allows attackers to recover the data.
The weakness was shared 12/31/2004 by First Last (Website). The advisory is shared at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2004-2591 since 11/29/2005. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After even before and not, there has been an exploit disclosed. 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.
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 databases at X-Force (18692), SecurityFocus (BID 12117†), OSVDB (12595†), Secunia (SA13630†) and SecurityTracker (ID 1012701†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.0
VulDB Temp Score: 4.0
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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
12/25/2004 🔍12/25/2004 🔍
12/25/2004 🔍
12/27/2004 🔍
12/27/2004 🔍
12/31/2004 🔍
12/31/2004 🔍
11/29/2005 🔍
03/09/2015 🔍
07/19/2017 🔍
Sources
Advisory: archives.neohapsis.comResearcher: First Last
Status: Not defined
CVE: CVE-2004-2591 (🔍)
GCVE (CVE): GCVE-0-2004-2591
GCVE (VulDB): GCVE-100-23469
X-Force: 18692 - CleanCache allows attacker to obtain information
SecurityFocus: 12117 - ButtUglySoftware CleanCache Insecure Data Removal Vulnerability
Secunia: 13630 - CleanCache "Secure File Deletion" Data Exposure Weakness, Less Critical
OSVDB: 12595 - CleanCache Secure File Deletion Data Disclosure
SecurityTracker: 1012701 - CleanCache Fails to Wipe Files
Entry
Created: 03/09/2015 16:55Updated: 07/19/2017 09:46
Changes: 03/09/2015 16:55 (56), 07/19/2017 09:46 (9)
Complete: 🔍
Cache ID: 216::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.