agentleFS
ferr079ferr079/claude-code-cybersec-skills/skills/privesc-linux/SKILL.md

privesc-linux

Skill0 starsChanged 31 days agoMITView on GitHub

Enumerate and exploit Linux privilege escalation paths: SUID binaries, sudo rules, capabilities, cron jobs, kernel exploits. Use on an authorized engagement or CTF box after landing a low-privilege shell.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When conducting security assessments that involve performing privilege escalation on linux

    line 18
  2. Distinctive:

    When following incident response procedures for related security events

    line 19
  3. Distinctive:

    When performing scheduled security testing or auditing activities

    line 20
  4. Distinctive:

    When validating security controls through hands-on testing

    line 21
  5. Distinctive:

    T1543.002: - Create or Modify System Process: Systemd Service

    line 37
  6. Distinctive:

    Check GTFOBins for exploitation methods

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Performing Privilege Escalation on Linux

Legal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.

Overview

Linux privilege escalation involves elevating from a low-privilege user account to root access on a compromised system. Red teams exploit misconfigurations, vulnerable services, kernel exploits, and weak permissions to achieve root. This skill covers both manual enumeration techniques and automated tools for identifying and exploiting privilege escalation vectors.

When to Use

  • When conducting security assessments that involve performing privilege escalation on linux
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Familiarity with red teaming concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

MITRE ATT&CK Mapping

  • T1548.001 - Abuse Elevation Control Mechanism: Setuid and Setgid
  • T1548.003 - Abuse Elevation Control Mechanism: Sudo and Sudo Caching
  • T1068 - Exploitation for Privilege Escalation
  • T1574.006 - Hijack Execution Flow: Dynamic Linker Hijacking
  • T1053.003 - Scheduled Task/Job: Cron
  • T1543.002 - Create or Modify System Process: Systemd Service

Key Escalation Vectors

SUID/SGID Binaries

  • Find SUID binaries: find / -perm -4000 -type f 2>/dev/null
  • Check GTFOBins for exploitation methods
  • Custom SUID binaries may have vulnerabilities

Sudo Misconfigurations

  • sudo -l to list allowed commands
  • Wildcards in sudo rules allow injection
  • NOPASSWD entries for dangerous commands
  • sudo versions vulnerable to CVE-2021-3156 (Baron Samedit)

Kernel Exploits

  • Dirty Cow (CVE-2016-5195) for older kernels
  • Dirty Pipe (CVE-2022-0847) for kernel 5.8+
  • PwnKit (CVE-2021-4034) for pkexec
  • GameOver(lay) (CVE-2023-2640, CVE-2023-32629) for Ubuntu

Cron Job Abuse

  • World-writable cron scripts
  • PATH hijacking in cron jobs
  • Wildcard injection in cron commands

Capabilities

  • getcap -r / 2>/dev/null to find binaries with capabilities
  • cap_setuid allows UID manipulation
  • cap_dac_override bypasses file permissions

Writable Service Files

  • Systemd unit files with weak permissions
  • Init scripts writable by non-root users
  • Socket files in accessible locations

Tools and Resources

ToolPurpose
LinPEASAutomated privilege escalation enumeration
LinEnumLinux enumeration script
linux-exploit-suggesterKernel exploit matching
pspyProcess monitoring without root
GTFOBinsSUID/sudo binary exploitation reference
PEASS-ngPrivilege escalation awesome scripts suite

Validation Criteria

  • Enumeration performed using automated tools
  • Privilege escalation vector identified
  • Root access achieved through identified vector
  • Evidence documented (screenshots, command output)
  • Alternative escalation paths identified

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.