Users Can Create ADIDNS Records
Any domain user can add records to Active Directory-integrated DNS zones, so an attacker can make unused or wildcard names resolve to a host they control and intercept traffic.
| Severity | Medium |
| CVSS 3.1 | 4.2 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 2.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-732: Incorrect Permission Assignment for Critical Resource |
| OWASP Top 10 | A01:2025 Broken Access Control |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle |
| Category | Security Misconfiguration |
Description
Active Directory-integrated DNS zones store each record as a dnsNode object in the directory, and access to them is controlled by Active Directory permissions. By default, Authenticated Users hold the Create all child objects permission on these zones, so that domain computers can register their own records through secure dynamic update. The same permission lets any domain user create a record for any name that does not yet exist, either with a dynamic DNS update or by writing a dnsNode object directly over LDAP, and become that record's owner. Records that already exist and belong to other accounts cannot be changed in this way.
An attacker with any domain account can use this to redirect clients to a host they control: by adding a wildcard record (*), which answers for every name in the zone that has no record of its own, or records for names that clients still look up but that no longer exist, such as decommissioned servers referenced in scripts and drive mappings. Unlike LLMNR and NetBIOS name poisoning, this works across subnets, does not depend on those protocols being enabled, and is served to every client by the domain's own DNS servers. The attacker can then capture NTLM authentication from those clients to crack offline or relay to other services, and serve their own content to clients that connect. The effect depends on what clients look up and on the protection of the services they authenticate to, and is greatest where SMB and LDAP signing are not required and NTLM is widely used. A wildcard record also changes the answer for every mistyped or missing name, which can disrupt applications and draw attention.
The permission is identified by reviewing the security of the zone objects in the DomainDnsZones and ForestDnsZones application partitions, and of any zones stored in the domain partition. It can be confirmed by adding a test record as an ordinary user, for example with Powermad or the dnstool.py script from krbrelayx, and removing it afterwards.
Remediation
- Remove the Create all child objects permission held by Authenticated Users on each Active Directory-integrated zone (on the zone's Security tab in DNS Manager, or with ADSI Edit), and grant it only to the principals that must register new records, such as Domain Computers or the account the DHCP servers use to register records on behalf of clients. Test the change on one zone first, as it stops other accounts from registering new names.
- Set
ms-DS-MachineAccountQuotato 0, so that an attacker cannot create a computer account to regain the permission through Domain Computers. - Find clients that still look up names that no longer exist, for example from DNS server analytical logs, and correct their configuration.
- Audit the creation of
dnsNodeobjects (Audit Directory Service Changes, event 5137) in the DNS application partitions, and alert on wildcard records and on records created by user accounts rather than computers or DHCP servers. - Reduce the value of any intercepted authentication by requiring SMB signing, enforcing LDAP signing and channel binding, and restricting NTLM.
Confirm the fix by attempting to add a record as an ordinary user, which should now be refused, and by checking that computers still register their records and that no unexpected wildcard records remain in any zone.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.