| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in mhc-utils 0.25 Snap2001-06-25. It has been classified as problematic. This affects an unknown function of the component adb2mhc. Performing a manipulation results in symlink. This vulnerability was named CVE-2003-0120. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in mhc-utils 0.25 Snap2001-06-25. It has been classified as problematic. This affects an unknown code block of the component adb2mhc. The manipulation with an unknown input leads to a symlink vulnerability. CWE is classifying the issue as CWE-61. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. This is going to have an impact on integrity. The summary by CVE is:
adb2mhc in the mhc-utils package before 0.25+20010625-7.1 allows local users to overwrite arbitrary files via a symlink attack on a default temporary directory with a predictable name.
The weakness was presented 03/07/2003 with Debian (Website). The advisory is shared at debian.org. This vulnerability is uniquely identified as CVE-2003-0120. The exploitability is told to be difficult. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 15093 (Debian DSA-256-1 : mhc - insecure temporary file), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l.
Upgrading to version 0.25+20010625-7.1 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (11439), Tenable (15093) and SecurityFocus (BID 6978†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.9VulDB Meta Temp Score: 2.8
VulDB Base Score: 2.9
VulDB Temp Score: 2.8
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: SymlinkCWE: CWE-61 / CWE-59
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 |
Nessus ID: 15093
Nessus Name: Debian DSA-256-1 : mhc - insecure temporary file
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
OpenVAS ID: 53331
OpenVAS Name: Debian Security Advisory DSA 256-1 (mhc)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: mhc-utils 0.25+20010625-7.1
Timeline
02/28/2003 🔍02/28/2003 🔍
03/07/2003 🔍
03/07/2003 🔍
09/29/2004 🔍
08/07/2014 🔍
07/15/2024 🔍
Sources
Advisory: debian.orgOrganization: Debian
Status: Not defined
CVE: CVE-2003-0120 (🔍)
GCVE (CVE): GCVE-0-2003-0120
GCVE (VulDB): GCVE-100-20193
X-Force: 11439
SecurityFocus: 6978 - mhc-utils Insecure Temporary File Creation Vulnerability
Entry
Created: 08/07/2014 18:16Updated: 07/15/2024 09:16
Changes: 08/07/2014 18:16 (63), 04/22/2019 06:33 (1), 07/15/2024 09:16 (17)
Complete: 🔍
Cache ID: 216:62E: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.