Timecop WMCube GDK 0.98 Object Description File wmcube-gdk memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Timecop WMCube GDK 0.98. Affected by this vulnerability is an unknown functionality of the file wmcube-gdk of the component Object Description File Handler. The manipulation results in memory corruption. This vulnerability is cataloged as CVE-2001-1201. There is no exploit available.
Details
A vulnerability was found in Timecop WMCube GDK 0.98. It has been classified as critical. Affected is some unknown functionality of the file wmcube-gdk of the component Object Description File Handler. 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 confidentiality, integrity, and availability. CVE summarizes:
Buffer overflow in wmcube-gdk for WMCube/GDK 0.98 allows local users to execute arbitrary code via long lines in the object description file.
The weakness was shared 12/17/2001 by Gobbles (Website). The advisory is available at securityfocus.com. This vulnerability is traded as CVE-2001-1201. The exploitability is told to be easy. Local access is required to approach this attack. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
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 (7720) and SecurityFocus (BID 3706†). 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: 9.3VulDB Meta Temp Score: 9.3
VulDB Base Score: 9.3
VulDB Temp Score: 9.3
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
12/17/2001 🔍12/17/2001 🔍
12/17/2001 🔍
07/11/2014 🔍
10/21/2024 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Gobbles
Status: Not defined
Confirmation: 🔍
CVE: CVE-2001-1201 (🔍)
GCVE (CVE): GCVE-0-2001-1201
GCVE (VulDB): GCVE-100-17754
X-Force: 7720
SecurityFocus: 3706 - WMCube/GDK Object File Buffer Overflow Vulnerability
Entry
Created: 07/11/2014 11:45Updated: 10/21/2024 09:21
Changes: 07/11/2014 11:45 (45), 04/10/2019 14:22 (7), 10/21/2024 09:21 (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.