Beyond ACLs Mapping Windows Privilege Escalation Paths with ... #1848
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.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
This post explains (1) how Windows authorization normally works via access tokens and ACLs, (2) why some token privileges can bypass DACL checks and become practical local privilege-escalation primitives, and (3) how BloodHound/SharpHound contributions let you enumerate privileges and logon rights domain-wide to find privilege-based escalation paths.
Windows uses access tokens to represent the security context of a process or thread. Key attribut...
🔧 Technical Details
Privilege-based privesc on Windows: treat token privileges as escalation primitives because they can bypass normal DACL authorization. SeBackupPrivilege can enable reading protected files/registry hives regardless of DACLs, allowing SAM/SYSTEM extraction and offline hash recovery (e.g., secretsdump tooling) to gain administrator access.
SeDebugPrivilege can bypass checks when opening process/thread handles, enabling actions like reading privileged process memory, injecting code, or dumping LSASS for credential extraction.
SeImpersonatePrivilege allows a thread to adopt another security context; SeAssignPrimaryTokenPrivilege enables creating new processes with primary tokens. Where direct token theft is blocked by assignment checks, these privileges can enable bypass. If SeDebugPrivilege is unavailable, Potato-family coercion techniques may be used to obtain an impersonation opportunity.
Enumeration approach: map privilege/logon-right assignments domain-wide by parsing GptTmpl.inf fr...
🤖 Agent Actions
Updated
windows-hardening/active-directory-methodology/bloodhound.mdwith a new section on domain-wide privilege and logon-right collection in BloodHound, including UAC/filtered-token caveats, GPO/SYSVOL parsing steps, LSA RPC enumeration, and an example SeBackupPrivilege abuse path. Added the blog as a reference.This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.