Musicqueue up to 1.1.1 Configuration File Language memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Musicqueue up to 1.1.1. This affects an unknown part of the component Configuration File. Performing a manipulation of the argument Language results in memory corruption. This vulnerability was named CVE-2003-1140. In addition, an exploit is available.
Details
A vulnerability was found in Musicqueue up to 1.1.1. It has been classified as very critical. This affects an unknown code of the component Configuration File. The manipulation of the argument language 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 confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in Musicqueue 1.2.0 allows local users to execute arbitrary code via a long language variable in the configuration file.
The weakness was presented 10/27/2003 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2003-1140 since 05/04/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 and a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/22/2024).
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
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 (13521), Exploit-DB (23303), SecurityFocus (BID 8903†), Secunia (SA10104†) and SecurityTracker (ID 1008014†). See VDB-20912 for similar entry. 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: 10.0VulDB Meta Temp Score: 9.1
VulDB Base Score: 10.0
VulDB Temp Score: 9.1
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/27/2003 🔍10/27/2003 🔍
10/27/2003 🔍
10/28/2003 🔍
10/30/2003 🔍
05/04/2005 🔍
08/15/2014 🔍
11/22/2024 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2003-1140 (🔍)
GCVE (CVE): GCVE-0-2003-1140
GCVE (VulDB): GCVE-100-20913
X-Force: 13521 - Musicqueue getConf function buffer overflow
SecurityFocus: 8903 - Musicqueue Multiple Buffer Overrun Vulnerabilities
Secunia: 10104 - Musicqueue Privilege Escalation Vulnerabilities, Less Critical
SecurityTracker: 1008014
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/15/2014 15:54Updated: 11/22/2024 03:38
Changes: 08/15/2014 15:54 (57), 06/15/2018 08:07 (6), 11/22/2024 03:38 (21)
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.