adcs_request: allow embedding a SAN URL entry to satisfy strong certificate binding requirements #40
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.
With recent Microsoft patches strong certificate binding is enforced.
This pull request adds a new option to the
adcs_request
BOF which allows to specify an URL entry to be added to the SAN. This allows to add the target's SID using the Microsoft specific prefix (tag:microsoft.com,2022-09-14:sid:
) to satisfy strong binding requirements.All commands below were run in a Ludus lab with the ADCS role applied.
Behavior before the proposed changes, try to abuse ESC1:
Show the SAN of the requested certificate:
Authentication fails because strong certificate binding is not satisfied:
Instead, request a certificate using the patched BOF and supply the targets SID in a Microsoft specific SAN URL entry:
Verify that the resulting certificate contains the expected SAN entries:
This time authentication succeeds:
The changes were also tested for machine accounts:
Show resulting SAN:
Authenticate: