Add support for enumerating templates over HTTP with ntlmrelayx #110
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
- Added `--enum-templates` for ADCS options
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Original PR on fortra/impacket: fortra#1879
Adds the ability to enumerate ADCS templates using only HTTP with a relayed user. Useful in the event that LDAP signing is enforced and LDAP channel binding is set up properly, but ESC8 is still present. Previously, you would have needed another way to enumerate certificate names (or attempt to blindly hit
ClientorMachinetemplates with your fingers crossed).Note that the HTTP endpoint doesn't give back verbose details like
EnrolleeSuppliesSubject, etc. so its still only a way to get accessible/enabled certificate templates only.--enum-templatesfor ADCS optionsDefault behavior
With debug