CVE-2005-0037: The DNS implementation of DNRD before 2.10 allows remote attackers to cause a denial of service via a compress

Routine

MEDIUM 5.0DOWNGRADE

CVE-2005-0037 is a medium-severity flaw (CVSS 5.0) affecting dnrd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The DNS implementation of DNRD before 2.10 allows remote attackers to cause a denial of service via a compressed DNS packet with a label length byte with an incorrect offset, which could trigger an infinite loop.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Published	2005-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: dnrd

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:10 UTCUpdated Record last modified

dnrd dnrd DOWNGRADE

Affected: 1.0 · 1.1 · 1.2 · 1.3 · 1.4 · 2.0 · 2.1 · 2.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy dnrd || rpm -q dnrd || dnrd --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison dnrd sudo apt install dnrd=<VERSION_BEFORE_1.0> sudo apt-mark hold dnrd

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list dnrd sudo dnf downgrade dnrd-<VERSION_BEFORE_1.0> sudo dnf versionlock add dnrd

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-0037?

dnrd: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-0037 being exploited?

CVE-2005-0037 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-0037 affect?

CVE-2005-0037 affects dnrd. Severity is medium (CVSS 5.0). The DNS implementation of DNRD before 2.10 allows remote attackers to cause a denial of service via a compressed DNS packet with a label length byte with an incorrect offset, which could trigger an infinite loop.

How urgent is CVE-2005-0037?

Priority 37/100. No elevated risk signals yet.

Related CVEs

CVE-2005-2316 MEDIUM 5.0 DOWNGRADE Domain Name Relay Daemon (DNRD) before 2.19.1 allows remote attackers to cause a denial of service (infinite r
CVE-2005-2315 HIGH 7.5 DOWNGRADE Buffer overflow in Domain Name Relay Daemon (DNRD) before 2.19.1 allows remote attackers to execute arbitrary
CVE-2004-0789 MEDIUM 5.0 DOWNGRADE DOWNGRADE Multiple implementations of the DNS protocol, including (1) Poslib 1.0.2-1 and earlier as used by Posadis, (2)
CVE-2002-0140 HIGH 7.5 DOWNGRADE Domain Name Relay Daemon (dnrd) 2.10 and earlier allows remote malicious DNS sites to cause a denial of servic

References

← Back to latest CVEs