# CVE-1999-1499: ISC BIND symlink vulnerability in named_dump.db and named.stats

Source: https://junglewise.ai/threats/cve-1999-1499-isc-bind-symlink-vulnerability-in-named-dump-db-and-named-stats  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 1998-04-10. Updated: 2026-05-10  
License: CC BY 4.0 with a link back

CVE-1999-1499 · Severity: low · CVSS 2.1 · Published 1998-04-10

ISC BIND is a widely used system for translating human-readable domain names into IP addresses. A security flaw in older versions allows a local user on the server to trick the system into overwriting or destroying sensitive files. This occurs when the system administrator stops the service, potentially leading to data loss or system instability.

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

## 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

## References

- [http://www.securityfocus.com/archive/1/8966](http://www.securityfocus.com/archive/1/8966)
- [http://www.securityfocus.com/bid/80](http://www.securityfocus.com/bid/80)

## 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)