Domain Name Relay Daemon up to 2.10 DNS Reply parse_query/get_objectname memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Domain Name Relay Daemon up to 2.10. It has been classified as critical. This affects the function parse_query/get_objectname of the component DNS Reply Handler. This manipulation causes memory corruption.
This vulnerability is tracked as CVE-2002-0140. Moreover, an exploit is present.
Details
A vulnerability classified as critical was found in Domain Name Relay Daemon up to 2.10. Affected by this vulnerability is the function parse_query/get_objectname of the component DNS Reply Handler. 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:
Domain Name Relay Daemon (dnrd) 2.10 and earlier allows remote malicious DNS sites to cause a denial of service and possibly execute arbitrary code via a long or malformed DNS reply, which is not handled properly by parse_query, get_objectname, and possibly other functions.
The weakness was disclosed 03/25/2002 by Andrew (Website). The advisory is shared at online.securityfocus.com. This vulnerability is known as CVE-2002-0140. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of 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 (7957), Exploit-DB (21236) and SecurityFocus (BID 3928†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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
01/20/2002 🔍03/25/2002 🔍
03/25/2002 🔍
07/11/2014 🔍
02/17/2025 🔍
Sources
Advisory: online.securityfocus.com⛔Researcher: Andrew
Status: Not defined
CVE: CVE-2002-0140 (🔍)
GCVE (CVE): GCVE-0-2002-0140
GCVE (VulDB): GCVE-100-18037
X-Force: 7957 - DNRD DNS request and reply denial of service
SecurityFocus: 3928 - DNRD DNS Request/Reply Denial Of Service Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/11/2014 13:47Updated: 02/17/2025 08:44
Changes: 07/11/2014 13:47 (50), 04/12/2019 09:15 (3), 02/17/2025 08:44 (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.