pam auth backdoor#21516
Open
h00die wants to merge 2 commits into
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
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.
This module allows a user to upload a pam so file (or compile on system if not x64) into the auth chain. If a user provides the secret password (generated at random) then auth is successful for any user. If they don't use the secret password, auth will default back to the original methods. This effectively backdoors all accounts on the system if a password is required (ssh password auth, sudo, su, etc etc).
Claude assisted with this module.
Verification
use post/linux/manage/pam_backdoorset SESSION <id>set BACKDOOR_PASS [password]runssh -p 2222 user@127.0.0.1and enter[password]— login succeeds