Ares FileShare 1.1 Configuration File ares.conf History stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Ares FileShare 1.1. This affects an unknown function of the file ares.conf of the component Configuration File. The manipulation of the argument History leads to stack-based overflow. This vulnerability is listed as CVE-2005-2425. There is no available exploit.
Details
A vulnerability, which was classified as very critical, has been found in Ares FileShare 1.1. This issue affects some unknown processing of the file ares.conf of the component Configuration File. The manipulation of the argument history with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Stack-based buffer overflow in Ares FileShare 1.1 allows remote attackers or local users to execute arbitrary code via a (1) long history parameter in the configuration file (ares.conf) or (2) long search string.
The weakness was presented 08/03/2005 by kozan (Website). The advisory is shared at marc.theaimsgroup.com. The identification of this vulnerability is CVE-2005-2425 since 08/03/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD at the moment (estimation calculated on 07/10/2018).
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 (21818), SecurityFocus (BID 14377†) and SecurityTracker (ID 1014576†). 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: 10.0VulDB Meta Temp Score: 9.3
VulDB Base Score: 10.0
VulDB Temp Score: 9.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: Stack-based overflowCWE: CWE-121 / CWE-119
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
07/25/2005 🔍07/26/2005 🔍
08/03/2005 🔍
08/03/2005 🔍
08/03/2005 🔍
03/11/2015 🔍
07/10/2018 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: kozan
Status: Not defined
CVE: CVE-2005-2425 (🔍)
GCVE (CVE): GCVE-0-2005-2425
GCVE (VulDB): GCVE-100-25913
X-Force: 21818 - Ares Fileshare long string buffer overflow
SecurityFocus: 14377 - Ares Fileshare Remote Buffer Overflow Vulnerability
SecurityTracker: 1014576
Entry
Created: 03/11/2015 23:39Updated: 07/10/2018 08:58
Changes: 03/11/2015 23:39 (52), 07/10/2018 08:58 (7)
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.