GNU Data Display Debugger 3.3.1 Home memory corruption ⚔ [Disputed]

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GNU Data Display Debugger 3.3.1. The impacted element is an unknown function. This manipulation of the argument Home as part of Environment Variable causes memory corruption. This vulnerability is handled as CVE-2002-2099. There is not any exploit available. The actual existence of this vulnerability is currently in question.
Details
A vulnerability has been found in GNU Data Display Debugger 3.3.1 and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation of the argument HOME as part of a Environment Variable 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:
Buffer overflow in the GNU DataDisplay Debugger (DDD) 3.3.1 allows local users to execute arbitrary code and possibly gain privileges via a long HOME environment variable. NOTE: since DDD is not installed setuid or setgid, perhaps this issue should not be included in CVE.
The weakness was released 12/31/2002 (Website). The advisory is shared at securitytracker.com. This vulnerability is known as CVE-2002-2099 since 08/05/2005. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The real existence of this vulnerability is still doubted at the moment.
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 (7979) and SecurityTracker (ID 1003241†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.gnu.org/
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
01/15/2002 🔍12/31/2002 🔍
12/31/2002 🔍
08/05/2005 🔍
08/06/2014 🔍
04/20/2019 🔍
Sources
Vendor: gnu.orgAdvisory: securitytracker.com⛔
Status: Not defined
Disputed: 🔍
CVE: CVE-2002-2099 (🔍)
GCVE (CVE): GCVE-0-2002-2099
GCVE (VulDB): GCVE-100-19741
X-Force: 7979 - DDD HOME environment variable buffer overflow
SecurityTracker: 1003241
Entry
Created: 08/06/2014 10:19Updated: 04/20/2019 00:43
Changes: 08/06/2014 10:19 (49), 04/20/2019 00:43 (5)
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.