Fix cracked credentials not displaying for multiple Kerberos hash types#37
Open
LSUDOKO wants to merge 1 commit intoh00die:krb5tgs_rc4from
Open
Fix cracked credentials not displaying for multiple Kerberos hash types#37LSUDOKO wants to merge 1 commit intoh00die:krb5tgs_rc4from
LSUDOKO wants to merge 1 commit intoh00die:krb5tgs_rc4from
Conversation
Owner
|
@LSUDOKO if you developed a test script, it can be handy to include that. Don't add it to the PR code change, but in a comment or the description |
Owner
|
Using the instructions in rapid7#21098 on how to recreate the issue, this did not solve the problem. Also, I don't think your intended solution would solve the problem as we can see two lines in the original issue: They have different |
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
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.
Fixes rapid7#21098
When multiple cracked cores exist for the same originating credential
(e.g., krb5tgs and krb5asrep cracked together), the display map was
overwriting entries. Changed to use ||= operator to keep the first
cracked core instead of overwriting it.
Since all cracked cores for the same hash have the same password data
(same private_id), displaying any one shows the correct cracked password.
This ensures both krb5tgs and krb5asrep credentials display their

cracked passwords correctly when cracked together.