# CVE-1999-0024: ISC BIND DNS cache poisoning via predictable query IDs

Source: https://junglewise.ai/threats/cve-1999-0024-isc-bind-dns-cache-poisoning-via-predictable-query-ids  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 1997-08-13. Updated: 2026-05-10  
License: CC BY 4.0 with a link back

CVE-1999-0024 · Severity: medium · CVSS 5 · Published 1997-08-13

ISC BIND is a widely used system for translating human-readable website names into IP addresses. A flaw in older versions allows attackers to redirect internet traffic to malicious servers by providing false information that the system then stores in its memory. This can lead to users being sent to fraudulent websites or having their email intercepted without their knowledge.

Technologies: [Isc Bind](https://junglewise.ai/threats/technologies/bind). Vendors: [Isc](https://junglewise.ai/threats/vendors/isc).

## Quick answers

**Is CVE-1999-0024 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-1999-0024 being exploited in the wild.

**How severe is CVE-1999-0024?** Medium severity, with a CVSS score of 5, published 13 August 1997.

**Which products and versions are affected?** ISC BIND.

**Is there a fix for CVE-1999-0024?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-1999-0024 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-1999-0024?** Check whether you run Isc Bind. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in ISC BIND due to the use of predictable transaction IDs (TXIDs) in DNS queries. An unauthenticated remote attacker can exploit this by predicting the next query ID and sending a forged DNS response to a recursive nameserver before the legitimate response arrives. If successful, the forged response is cached by the server, leading to DNS cache poisoning. This allows the attacker to spoof DNS records and redirect traffic for affected domains. The issue is a classic example of insufficient entropy in protocol identifiers.

## Affected products

- ISC BIND

## Timeline

- 1997-08-13: disclosed: Initial publication date

## References

- [https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0024](https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0024)

## Related threats

- [BIND assertion failure with redirect zone and qname-minimization](https://junglewise.ai/threats/cve-2026-96888-a-bind-resolver-that-is-configured-with-both-a-redirect-zone-and)
- [BIND named GSS-TSIG replay heap corruption](https://junglewise.ai/threats/cve-2026-94300-replaying-gss-tsig-signed-udp-messages-can-result-in-memory)
- [ISC BIND resolver DNS message processing denial of service](https://junglewise.ai/threats/cve-2026-19630-in-a-bind-resolver-inbound-dns-protocol-messages-with-a)
- [ISC BIND denial of service via TKEY queries](https://junglewise.ai/threats/cve-2015-5477-isc-bind-data-processing-errors-vulnerability)
- [BIND resolver crash on DNSSEC-signed wildcard with NSEC mismatch](https://junglewise.ai/threats/cve-2026-80274-bind-resolver-crash-on-dnssec-signed-wildcard-with-nsec-mismatch)