Dynamic DNS Misconfiguration Can Expose Sensitive Internal Network Data

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
Amazon Web Servicesdisclosed a vulnerability in DNS hosting services that affects millions of corporate endpoints. AWS and Google have already patched the vulnerability, but many other DNS providers and their customers mayGoogledisclosed a vulnerability in DNS hosting services that affects millions of corporate endpoints. AWS and Google have already patched the vulnerability, but many other DNS providers and their customers may still be at
Products
Amazon Route53urging DNS providers to fix the underlying nameserver hijacking issue that leaves customers exposed (Amazon Route53 and Google have already done so). But ultimately, customers are responsible for configuring their DNSMicrosoft WindowsThe Dynamic DNS Leak is a vulnerability affecting Windows endpoints that can expose Dynamic DNS traffic that should never leave an internal network. A malicious actor could exploit this vulnerability to learn your
