DC performing-privilege-escalation-on-linux
Guides manual enumeration and automated tooling to escalate from a low-privilege Linux user to root by exploiting misconfigurations, vulnerable services, kernel exploits, and weak permissions, mapped to MITRE ATT&CK. Use during authorized red team engagements or penetration tests once initial low-privilege access on a Linux host is obtained and root-level access is needed.
Guides manual enumeration and automated tooling to escalate from a low-privilege Linux user to root by exploiting misconfigurations, vulnerable services…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 22
✓ No critical or high findings
Medium and low: 22
-
medium Dangerous commands
cmd-persistencereferences/api-reference.md:31Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)Checks: /etc/passwd, /etc/shadow, /etc/sudoers, /etc/crontab, /root, cron dirs.
security skill -
medium Dangerous commands
cmd-persistencereferences/standards.md:24Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)- Ensure permissions on /etc/crontab are configured (600 root:root)
security skill -
medium Dangerous commands
cmd-persistencereferences/workflows.md:44Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)cat /etc/crontab
security skill -
medium Dangerous commands
cmd-persistencescripts/agent.py:97Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)interesting_paths = ["/etc/passwd", "/etc/shadow", "/etc/sudoers", "/etc/crontab",
code literal -
medium Dangerous commands
cmd-persistencescripts/agent.py:98Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)"/etc/cron.d", "/etc/systemd/system", "/root"]
code literal -
medium Dangerous commands
cmd-persistencescripts/agent.py:121Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)cron_paths = ["/etc/crontab", "/etc/cron.d", "/var/spool/cron/crontabs"]
code literal -
low Risky intent
intent-offensive-securityreferences/api-reference.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# API Reference — Performing Privilege Escalation on Linux
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:33Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### `check_cron_jobs()` — Cron job privilege escalation vectors
-
low Risky intent
intent-offensive-securityreferences/standards.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## MITRE ATT&CK - Privilege Escalation (TA0004)
-
low Dangerous commands
cmd-privilegereferences/standards.md:6Privilege escalation / world-writable permissions (documentation of a security skill)| T1548.001 | Setuid and Setgid | Exploit SUID/SGID binaries |
security skill -
low Risky intent
intent-offensive-securityreferences/standards.md:8Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| T1068 | Exploitation for Privilege Escalation | Kernel/service exploits |
-
low Risky intent
intent-offensive-securityreferences/workflows.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Linux Privilege Escalation Workflows
-
low Dangerous commands
cmd-cron-mentionreferences/workflows.md:46Mentions editing / listing crontab (documentation of a security skill)crontab -l
security skill -
low Dangerous commands
cmd-pipe-to-shell-known-hostreferences/workflows.md:65Pipe-to-shell installer from a well-known host (still executes remote code) (documentation of a security skill)curl -L https://github.com/peass-ng/PEASS-ng/releases/latest/download/linpeas.sh | sh
security skill -
low Dangerous commands
cmd-privilegereferences/workflows.md:106Privilege escalation / world-writable permissions (documentation of a security skill)# sudo python3
security skill -
low Dangerous commands
cmd-privilegereferences/workflows.md:107Privilege escalation / world-writable permissions (documentation of a security skill)sudo python3 -c 'import pty; pty.spawn("/bin/bash")'security skill -
low Risky intent
intent-offensive-securitySKILL.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use)and weak permissions, mapped to MITRE ATT&CK. Use during authorized red team engagements
-
low Risky intent
intent-offensive-securitySKILL.md:38Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Performing Privilege Escalation on Linux
-
low Risky intent
intent-offensive-securitySKILL.md:45Offensive-security / dual-use content (legitimate for authorised testing; review intended use)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 w
-
low Risky intent
intent-offensive-securitySKILL.md:50Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- When conducting security assessments that involve performing privilege escalation on linux
-
low Risky intent
intent-offensive-securitySKILL.md:57Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Familiarity with red teaming concepts and tools
-
low Dangerous commands
cmd-privilegeSKILL.md:64Privilege escalation / world-writable permissions (documentation of a security skill)- **T1548.001** - Abuse Elevation Control Mechanism: Setuid and Setgid
security skill
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "d3fend_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 825 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 375: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 39 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.