Menu

Individual skill

bypassing-restricted-shells

0upvotes

Escaping restricted/limited shells (rbash, rksh, lshell, chroot jails) and command-execution filters during authorized engagements - using interactive command launchers, environment/PATH abuse, command substitution and quoting/encoding tricks, SSH/SCP exec, GTFOBins, and language interpreters to regain a full shell.

internal/tools/skills/data/penetration-testing/bypassing-restricted-shells/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,329
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Bypassing Restricted Shells

## When to Use
- You land in a limited shell (`rbash`, `rksh`, `lshell`, `/bin/rbash`) where `cd`, `/`, `>`, and `PATH` changes are blocked.
- A vendor appliance, jump host, or kiosk SSH account drops you into a menu or restricted environment.
- You are inside a `chroot` jail and need to break out to the real filesystem.
- A web command-injection point filters spaces, slashes, or keywords and you need to smuggle a working command.

## Critical: Techniques Most Often Missed
- **SSH that never enters the restricted shell** — request a different shell or skip profile at login instead of fighting the jail.
  ```bash
  ssh -t user@<IP> bash                 # force an interactive bash directly
  ssh user@<IP> -t "bash --noprofile -i"
  ssh user@<IP> -t "() { :; }; sh -i "  # shellshock-style function trick
Back to top