-
Notifications
You must be signed in to change notification settings - Fork 563
[New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation #3535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Samirbous
approved these changes
Mar 26, 2024
Aegrah
approved these changes
Mar 27, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left suggestions; LGTM.
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
protectionsmachine
pushed a commit
that referenced
this pull request
Mar 27, 2024
…3535) * [New Rule] Potential ADIDNS Poisoning via Wildcard Record Creation * Update credential_access_adidns_wildcard.toml --------- Co-authored-by: Ruben Groenewoud <[email protected]> (cherry picked from commit 67e9ebf)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Active Directory Integrated DNS (ADIDNS) is one of the core components of AD DS, leveraging AD's access control and
replication to maintain domain consistency. It stores DNS zones as AD objects, a feature that, while robust, introduces
some security issues, such as wildcard records, mainly because of the default permission to create DNS-named records.
Attackers can create wildcard records to redirect traffic that doesn't explicitly match records contained in the zone,
becoming the Man-in-the-Middle and being able to abuse DNS similarly to LLMNR/NBNS spoofing.
Event Data