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