CVE-1999-0024: Medium severity ISC BIND vulnerability
DNS cache poisoning via BIND, by predictable query IDs.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Configure BIND to randomize DNS transaction (query) IDs so they are not predictable. Enable any available transaction ID/entropy/randomization settings in named.conf or the platform-specific BIND configuration.
BIND query ID randomization = enabled - Compensating control
Restrict access to recursive resolver functionality to trusted networks (use ACLs) or firewall rules to limit exposure to untrusted/Internet clients while fixes are applied.
- Operational
After enabling query ID randomization, flush the DNS cache and restart the BIND service to remove any potentially poisoned entries.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-0024?
CVE-1999-0024 is classified as a high-severity vulnerability due to the potential for DNS cache poisoning.
How do I fix CVE-1999-0024?
To fix CVE-1999-0024, upgrade to a newer version of BIND that implements unpredictable query IDs.
Which versions of BIND are affected by CVE-1999-0024?
CVE-1999-0024 affects BIND versions 4.9.5 and 8.1.
What is the impact of CVE-1999-0024?
The impact of CVE-1999-0024 includes the potential for attackers to redirect DNS queries to malicious servers.
What platforms are affected by CVE-1999-0024?
CVE-1999-0024 affects various platforms including BSD, IBM AIX, and SunOS among others.