Skip to main content
LowDNSOWASP A05:2021CWE-200

How to fix: Signed zone uses NSEC, allowing zone walking

The zone is DNSSEC-signed but publishes no NSEC3PARAM record, so it uses NSEC. NSEC provides authenticated denial of existence in a form that lets the zone's full contents be enumerated.

Why it matters

An NSEC record proves a name does not exist by naming the next name that does, so walking the chain returns the complete contents of the zone. Every internal hostname in it becomes public: vpn, jira, staging, backup, the lot. That is a full target list produced without sending a single request to any of those hosts.

This is a design property of NSEC rather than a misconfiguration, which is why NSEC3 was specified in the first place. Whether it matters depends on the zone: for one whose names are all public anyway it is close to irrelevant, and for one holding internal infrastructure names it hands over the network map. RFC 9276 recommends NSEC3 with zero iterations and an empty salt, which gives the enumeration resistance without the cost that made early NSEC3 deployments expensive.

How to fix it

  1. 1Switch to NSEC3 with zero iterations and an empty salt if the zone contains names you would rather not publish.
  2. 2Walk your own zone first to see what is actually exposed before deciding how urgent this is.
  3. 3For a zone of entirely public names, NSEC remains a reasonable choice; document the decision rather than leaving it implicit.

Code examples

See what an attacker would see

bash
ldns-walk example.com

BIND: move to NSEC3 with RFC 9276 parameters

bash
rndc signing -nsec3param 1 0 0 - example.com
# hash=1 (SHA-1), flags=0, iterations=0, salt=- (empty)

References

Detected automatically by VulnRadar. The check id is dns-nsec-zone-walking, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is Signed zone uses NSEC, allowing zone walking?
VulnRadar rates this low severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-nsec-zone-walking, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Signed zone uses NSEC, allowing zone walking map to?
It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for signed zone uses nsec, allowing zone walking

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Signed zone uses NSEC, allowing zone walking fix | VulnRadar