Tuomas Airaksinen midirecord 2.0 midirecord.cc daemon line memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Tuomas Airaksinen midirecord 2.0. Affected by this vulnerability is the function daemon of the file midirecord.cc. Executing a manipulation of the argument line can lead to memory corruption.
This vulnerability is registered as CVE-2006-3931. Furthermore, an exploit is available.
Details
A vulnerability was found in Tuomas Airaksinen midirecord 2.0. It has been declared as problematic. This vulnerability affects the function daemon of the file midirecord.cc. The manipulation of the argument line 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. CVE summarizes:
Buffer overflow in the daemon function in midirecord.cc in Tuomas Airaksinen Midirecord 2.0 allows local users to execute arbitrary code via a long command line argument (filename). NOTE: This may not be a vulnerability if Midirecord is not installed setuid.
The weakness was published 07/31/2006 by Dedi Dwianto (Website). The advisory is available at securityfocus.com. This vulnerability was named CVE-2006-3931 since 07/31/2006. The exploitation appears to be easy. Local access is required to approach this attack. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known.
A public exploit has been developed in ANSI C. It is possible to download the exploit at securityfocus.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 (28047), Exploit-DB (28288) and SecurityFocus (BID 19190†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.9
VulDB Temp Score: 5.4
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: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
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
07/27/2006 🔍07/31/2006 🔍
07/31/2006 🔍
07/31/2006 🔍
03/12/2015 🔍
02/02/2025 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Dedi Dwianto
Status: Not defined
CVE: CVE-2006-3931 (🔍)
GCVE (CVE): GCVE-0-2006-3931
GCVE (VulDB): GCVE-100-31570
X-Force: 28047 - Midirecord MIDI filename buffer overflow
SecurityFocus: 19190 - MidiRecord2 MidiRecord.CC Local Buffer Overflow Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 14:25Updated: 02/02/2025 15:42
Changes: 03/12/2015 14:25 (52), 08/01/2018 09:30 (8), 02/02/2025 15:42 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.