| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Deception Decfingerd 0.7. It has been rated as critical. Affected is an unknown function. The manipulation of the argument Username leads to memory corruption. This vulnerability is listed as CVE-2002-2091. There is no available exploit.
Details
A vulnerability was found in Deception Decfingerd 0.7 and classified as critical. This issue affects an unknown function. The manipulation of the argument Username with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Format string vulnerability in Deception Finger Daemon, decfingerd, 0.7 may allow remote attackers to execute arbitrary code via the username of a finger request.
The bug was discovered 06/25/2002. The weakness was presented 12/31/2002 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2002-2091 since 08/05/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 189 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 31014 (DECFingerD Format String Vulnerability).
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 (9434), SecurityFocus (BID 5105†), OSVDB (19474†) and Vulnerability Center (SBV-10397†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/25/2002 🔍06/25/2002 🔍
06/25/2002 🔍
12/31/2002 🔍
12/31/2002 🔍
08/05/2005 🔍
02/21/2006 🔍
08/06/2014 🔍
08/30/2025 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2002-2091 (🔍)
GCVE (CVE): GCVE-0-2002-2091
GCVE (VulDB): GCVE-100-19733
X-Force: 9434
SecurityFocus: 5105 - DECFingerD Format String Vulnerability
OSVDB: 19474 - DECFingerD - Format String Vulnerability
Vulnerability Center: 10397 - Deception Finger Daemon Format String Vulnerability via Username, Critical
Entry
Created: 08/06/2014 10:16Updated: 08/30/2025 11:19
Changes: 08/06/2014 10:16 (57), 06/14/2019 11:14 (4), 08/30/2025 11:19 (18)
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.