Fix when cert server does not request NTLM auth #1
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.
Bumped into this scenario on a pentest and made a couple edits to allow the ADCS attack to still run.
If the IIS cert server is configured to allow anonymous authentication and Windows NTLM auth, the cert server will default to anonymous auth and will not prompt for NTLM authentication.
When ntlmrelayx encounters this, it won't relay the authentication because it's not requested by the cert server:
I've added a small fix into the
httprelayclient
to send NTLM authentication, even if not requested, when performing the ADCS attack. This allows the attack to generate a certificate:Also added in some code from this implementation of the attack to prevent clients from being attacked multiple times and causing multiple certificates to be generated.