| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Dameng DM Database Server. It has been classified as critical. This vulnerability affects unknown code in the library wdm_dll.dll. This manipulation causes memory corruption. This vulnerability is registered as CVE-2010-2159. Furthermore, an exploit is available.
Details
A vulnerability was found in Dameng DM Database Server (Database Software) (unknown version). It has been declared as critical. Affected by this vulnerability is an unknown code block in the library wdm_dll.dll. The manipulation 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. The summary by CVE is:
Dameng DM Database Server allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors related to the SP_DEL_BAK_EXPIRED procedure in wdm_dll.dll, which triggers memory corruption.
The weakness was published 06/07/2010 with Symantec (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2010-2159 since 06/07/2010. The exploitation appears to be easy. The attack can be launched remotely. The requirement for exploitation is a single authentication. Technical details and also a public exploit are known.
It is possible to download the exploit 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 (59081), Exploit-DB (34058) and SecurityFocus (BID 40460†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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
05/31/2010 🔍06/07/2010 🔍
06/07/2010 🔍
06/07/2010 🔍
03/19/2015 🔍
12/10/2024 🔍
Sources
Advisory: securityfocus.com⛔Organization: Symantec
Status: Not defined
CVE: CVE-2010-2159 (🔍)
GCVE (CVE): GCVE-0-2010-2159
GCVE (VulDB): GCVE-100-53485
X-Force: 59081
SecurityFocus: 40460 - DM Database Server 'SP_DEL_BAK_EXPIRED' Memory Corruption Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/19/2015 12:22Updated: 12/10/2024 11:24
Changes: 03/19/2015 12:22 (49), 03/27/2019 10:54 (3), 12/10/2024 11:24 (27)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.