linux-privilege-escalation

Enumerate Linux misconfigurations and select privilege escalation paths to root.

5|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/DorianGallo/hack-skills-local --skill linux-privilege-escalation-doriangallo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-privilege-escalation
Source: https://github.com/DorianGallo/hack-skills-local/tree/main/skills/linux-privilege-escalation
Command: npx skills add https://github.com/DorianGallo/hack-skills-local --skill linux-privilege-escalation-doriangallo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

It helps you systematically escalate privileges on Linux from a low-privilege shell to root by enumerating misconfigurations and exploit paths across SUID/SGID, capabilities, scheduled tasks, sensitive file permissions, and kernel weaknesses.

Core Features & Use Cases

  • Privilege escalation decision flow: guides you through a practical order of operations to find the most promising escalation vector (sudo, SUID/SGID, capabilities, cron, writable files, Docker/NFS).
  • Technique coverage for common Linux paths: supports exploitation and abuse patterns such as LD_PRELOAD/environment leakage, writable cron jobs with PATH/wildcard tricks, Docker group breakout, and NFS no_root_squash.
  • Kernel exploit mapping and readiness: includes a kernel-version-to-exploit checklist plus compilation/cross-compilation and stability guidance to avoid chasing incompatible CVEs.
  • Use Case: You land on a foothold host with a constrained user shell; run this workflow to identify a direct escalation route (e.g., capability or SUID abuse), then move to kernel mapping only when higher-probability vectors fail.

Quick Start

Use the linux-privilege-escalation skill to enumerate SUID/capabilities/cron writable paths and select the best escalation path for the current host.

Frequently Asked Questions about linux-privilege-escalation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I escalate privileges on Linux from a low-privilege shell to root?

Linux privilege escalation from a low-privilege shell requires enumerating misconfigurations using a structured decision tree, checking sudo permissions, SUID/SGID binaries, capabilities, and cron jobs to identify the most promising exploitation vector.

What is the best way to enumerate SUID binaries and Linux capabilities for privilege escalation?

Enumerating SUID binaries and Linux capabilities for privilege escalation involves running targeted checks like sudo -l, SUID/SGID searches, and getcap to discover exploitable misconfigurations and apply the correct abuse technique based on findings.

When do I need to use kernel exploits for Linux privilege escalation?

Kernel exploits for Linux privilege escalation are used when higher-probability vectors like SUID, capabilities, and cron abuse fail, requiring a kernel-version-to-exploit checklist plus compilation guidance and stability risk assessment for outdated versions.

Can I abuse cron jobs and writable file permissions to escalate privileges on Linux?

Abusing cron jobs and writable file permissions for Linux privilege escalation is possible by exploiting misconfigurations through PATH/wildcard tricks and sensitive file discovery to execute targeted checks and apply the correct technique based on findings.

Does this workflow cover Docker breakout and NFS no_root_squash exploitation paths?

This workflow covers Docker breakout and NFS no_root_squash exploitation paths as part of its technique coverage for common Linux paths, guiding exploitation and abuse patterns for Docker group breakout and NFS misconfigurations.

What are the limitations of using environment and library injection for Linux privilege escalation?

Limitations of using environment and library injection for Linux privilege escalation include dependency on specific misconfigurations like LD_PRELOAD leakage, requiring targeted checks of sudo permissions and sensitive file permissions before applying the correct technique.