Xmlstarlet Command Line Xml Toolkit 0.9.3 xml_elem.c memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Xmlstarlet Command Line Xml Toolkit 0.9.3. The affected element is an unknown function of the file xml_elem.c. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2004-2160. There is no available exploit.
Details
A vulnerability was found in Xmlstarlet Command Line Xml Toolkit 0.9.3. It has been classified as critical. This affects an unknown functionality of the file xml_elem.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity, and availability. The summary by CVE is:
Format string vulnerability in xml_elem.c for XMLStarlet Command Line XML Toolkit 0.9.3 may allow attackers to cause a denial of service or execute arbitrary code.
The weakness was presented 12/31/2004 (Website). The advisory is shared at sourceforge.net. This vulnerability is uniquely identified as CVE-2004-2160 since 07/10/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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.
See VDB-23072 for similar entry. 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: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.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: Memory corruptionCWE: 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
12/31/2004 🔍12/31/2004 🔍
07/10/2005 🔍
03/09/2015 🔍
07/17/2017 🔍
Sources
Advisory: sourceforge.netStatus: Not defined
Confirmation: 🔍
CVE: CVE-2004-2160 (🔍)
GCVE (CVE): GCVE-0-2004-2160
GCVE (VulDB): GCVE-100-23073
See also: 🔍
Entry
Created: 03/09/2015 15:52Updated: 07/17/2017 09:33
Changes: 03/09/2015 15:52 (42), 07/17/2017 09:33 (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.