Dynamic DNS Misconfiguration Can Expose Sensitive Internal Network Data

· Original article ↗

Summary

Wiz researchers disclosed a Dynamic DNS vulnerability that can expose internal network details from Windows endpoints. AWS and Google have patched the issue; organizations should check and properly configure their DNS settings.

Key points

  • Wiz researchers say misconfigured Dynamic DNS can expose traffic that should remain inside an organization's network.
  • Potentially exposed information includes computer names, internal and external IP addresses, and employee names and locations.
  • AWS and Google have patched the underlying nameserver hijacking issue; other DNS providers and customers may remain at risk.
  • Wiz's free Dynamic DNS Checker examines a domain's SOA record and, if misconfigured, checks for suspicious nameserver domains as an indicator of exploitation risk.
  • Wiz advises configuring public DNS SOA records to point to an invalid domain the organization owns or to a valid internal Dynamic DNS server.

Article Details

Vulnerability Types
  • Dynamic DNS data exposure caused by DNS resolver misconfiguration and nameserver hijacking
Exploitation Status
unknown
Exploit Availability
unknown
Patch Status
partial
Workarounds
  • Configure public DNS provider SOA records to point to an invalid domain the organization owns or to a valid internal Dynamic DNS server.
  • Configure DNS resolvers so Dynamic DNS updates do not leave the internal network.

Vendors

Products

Tools

Related Articles