Adding PRT capabilities#10
Open
fjodoin wants to merge 2 commits intoabsolomb:mainfrom
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Attackers may add fake devices to Entra/Intune upon successfully phishing a target. If this is done through Device Code Phishing, the attacker may never obtain access to the cleartext credentials of the victim.
The fake device can be used to obtain PRTs. It is important for defenders to understand where Network Restrictions are missing on CAPs. Fake devices (and their PRTs) can potentially spoof Compliance, Hybrid, Passwordless, etc. authentication contexts.
This vibe-coded and tested branch adds the PRT functionality, allowing defenders to spray PRTs; Attackers can also perform CAP bruteforcing using PRTs without ever obtaining the victim's cleartext passwords.