Quick answers
- Is CVE-1999-1499 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-1999-1499 being exploited in the wild.
- How severe is CVE-1999-1499?
- Low severity, with a CVSS score of 2.1, published 10 April 1998.
- Which products and versions are affected?
- Isc Bind 4.9, 8.1.
- Is there a fix for CVE-1999-1499?
- 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-1499 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-1999-1499?
- Check whether you run Isc Bind at an affected version. 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
A symbolic link (symlink) vulnerability exists in ISC BIND versions 4.9 and 8.1. When the 'named' process receives a SIGINT or SIGIOT signal, it attempts to write debug or statistics information to 'named_dump.db' or 'named.stats' in a predictable location. A local attacker can create a symbolic link with one of these filenames pointing to a critical system file. When the root user or a system process sends the termination signal, BIND follows the symlink and overwrites the target file with its own output, leading to unauthorized file modification or destruction.
Affected products
- ISC BIND 4.9, 8.1
Timeline
- 1998-04-10: disclosed
- 1998-04-10: advisory