PatchTheCVECVE-2003-0914: ISC BIND 8.3.x before 8.3.7, and 8.4.x before 8.4.3, allows remote attackers to poison the cache via a malicio
38
Routine
MEDIUM 4.3DOWNGRADEDOWNGRADEMITIGATE
CVE-2003-0914 is a medium-severity flaw (CVSS 4.3) affecting bind, namesurfer, tru64. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
ISC BIND 8.3.x before 8.3.7, and 8.4.x before 8.4.3, allows remote attackers to poison the cache via a malicious name server that returns negative responses with a large TTL (time-to-live) value.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 4.3 (Medium) |
| EPSS exploit chance | 3.8% (top 10%) |
| CISA exploited list | No |
| Published | 2003-12-15 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
isc bind DOWNGRADE
Affected: 8.2.3 · 8.2.4 · 8.2.5 · 8.2.6 · 8.2.7 · 8.3.0 · 8.3.1 · 8.3.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.2.3
1. Check installed version
apt-cache policy bind || rpm -q bind || bind --version
2. No fixed release: DOWNGRADE to a release before 8.2.3 (Debian / Ubuntu)
apt-cache madison bind
sudo apt install bind=<VERSION_BEFORE_8.2.3>
sudo apt-mark hold bind
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bind
sudo dnf downgrade bind-<VERSION_BEFORE_8.2.3>
sudo dnf versionlock add bind
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.
nixu namesurfer DOWNGRADE
Affected: standard_3.0.1 · suite_3.0.1
Fixed in: no fixed release known
Safe to downgrade to: a release before standard_3.0.1
1. Check installed version
apt-cache policy namesurfer || rpm -q namesurfer || namesurfer --version
2. No fixed release: DOWNGRADE to a release before standard_3.0.1 (Debian / Ubuntu)
apt-cache madison namesurfer
sudo apt install namesurfer=<VERSION_BEFORE_standard_3.0.1>
sudo apt-mark hold namesurfer
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list namesurfer
sudo dnf downgrade namesurfer-<VERSION_BEFORE_standard_3.0.1>
sudo dnf versionlock add namesurfer
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.
compaq tru64 MITIGATE
Affected: 4.0f · 4.0f_pk6_bl17 · 4.0f_pk7_bl18 · 4.0f_pk8_bl22 · 4.0g · 4.0g_pk3_bl17 · 4.0g_pk4_bl22 · 5.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.0f
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
freebsd freebsd MITIGATE
Affected: 4.4 · 4.5 · 4.6 · 4.6.2 · 4.7 · 4.8 · 4.9 · 5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.4
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
hp hp-ux MITIGATE
Affected: 11.00 · 11.11
Fixed in: no fixed release known
Safe to downgrade to: a release before 11.00
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
ibm aix MITIGATE
Affected: 5.1l
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.1l
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
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.
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-2003-0914?
bind: downgrade or apply the listed mitigation; namesurfer: downgrade or apply the listed mitigation; tru64: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2003-0914 being exploited?
CVE-2003-0914 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-2003-0914 affect?
CVE-2003-0914 affects bind, namesurfer, tru64. Severity is medium (CVSS 4.3). ISC BIND 8.3.x before 8.3.7, and 8.4.x before 8.4.3, allows remote attackers to poison the cache via a malicious name server that returns negative responses with a large TTL (time-to-live) value.
How urgent is CVE-2003-0914?
Priority 38/100. No elevated risk signals yet.
Software pages
Related CVEs
- CVE-2026-13321 HIGH 8.6 UPGRADE The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the si
- CVE-2026-13204 HIGH 7.5 UPGRADE If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RR
- CVE-2026-10723 MEDIUM 6.8 UPGRADE BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authentica
- CVE-2026-10822 MEDIUM 6.5 UPGRADE If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and m
- CVE-2026-11331 HIGH 7.5 UPGRADE An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names