Juan Cespedes ltrace 0.3.10 search_for_command memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Juan Cespedes ltrace 0.3.10. It has been classified as problematic. Affected by this issue is the function search_for_command. This manipulation causes memory corruption.
The identification of this vulnerability is CVE-2004-0172. There is no exploit available.
Details
A vulnerability has been found in Juan Cespedes ltrace 0.3.10 and classified as critical. Affected by this vulnerability is the function search_for_command. The manipulation with an unknown input 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:
Heap-based buffer overflow in the search_for_command function of ltrace 0.3.10, if it is installed setuid, could allow local users to execute arbitrary code via a long filename. NOTE: It is unclear whether there are any packages that install ltrace as a setuid program, so this candidate might be REJECTed.
The weakness was shared 03/15/2004 (Website). The advisory is shared at lists.grok.org.uk. This vulnerability is known as CVE-2004-0172 since 02/20/2004. The exploitation appears to be easy. An attack has to be approached locally. 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 databases at X-Force (13389), SecurityFocus (BID 8790†) and SecurityTracker (ID 1007896†). 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: 9.3VulDB Meta Temp Score: 9.0
VulDB Base Score: 9.3
VulDB Temp Score: 9.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: Memory corruptionCWE: CWE-119
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
10/07/2003 🔍10/07/2003 🔍
02/20/2004 🔍
03/15/2004 🔍
03/15/2004 🔍
10/15/2014 🔍
06/18/2018 🔍
Sources
Advisory: lists.grok.org.ukStatus: Not defined
CVE: CVE-2004-0172 (🔍)
GCVE (CVE): GCVE-0-2004-0172
GCVE (VulDB): GCVE-100-21649
X-Force: 13389 - ltrace search_for_command buffer overflow
SecurityFocus: 8790 - LTrace Local Command Line Parameter Heap Overflow Vulnerability
SecurityTracker: 1007896
Entry
Created: 10/15/2014 15:31Updated: 06/18/2018 09:10
Changes: 10/15/2014 15:31 (50), 06/18/2018 09:10 (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.