Repository navigation
Environment Breakout
Checklist for testing kiosk, thin-client, and restricted desktop environments for breakout to a full shell. No item in this list has an individual write-up in the original source material - every item links to the LOLBAS project (โ general reference), the standard living catalog of living-off-the-land binaries and techniques used for exactly this kind of restricted-environment breakout.
Purpose: Covers testing of restricted environments specifically - kiosks, Citrix/RDP published applications, locked-down thin clients, and any interface where a user is deliberately confined to a single application or limited desktop. This is a different threat model from typical privilege escalation: the starting point isn't "unprivileged shell access," it's "no shell access at all, just one sanctioned application window."
Function: The checklist works through breakout in roughly the order an attacker would attempt it: physical access and identification first (what's the platform, what's actually installed), then progressively more invasive escape techniques - abusing file/save dialogs and URI protocol handlers to spawn other processes, crashing the front-end to fall back to a desktop, exploiting browser extensions or Windows shell manipulation, and finally bypassing whatever software/group policy restrictions remain once a shell is reached.
Goal: Determine whether the restriction is enforced at a level that actually matters (application whitelisting, kernel-level sandboxing) or is purely cosmetic (a locked-down Explorer shell sitting on top of a fully capable, unrestricted OS). The end state being tested is: can a user with access to exactly one sanctioned application reach an arbitrary command shell, and from there, arbitrary code execution.
When & how to use this: Use this against any kiosk, terminal server published-app, or restricted-shell deployment during a physical or remote engagement - work through the list roughly top-to-bottom, since later items (privilege escalation, AppLocker bypass) generally assume you've already broken out to some kind of shell using an earlier item. Pair with AppLocker Bypass once you have shell access but application whitelisting is still in the way.
๐ Companion deep-dive on the same LOLBins/LOLScripts: Tradecraft/lolbins-lolbas.md
- EB-001 - Physical Security of the Device โ
- EB-002 - Platform Identification and Version Software in Use โ
- EB-003 - Enumeration of Windows Boxes Available โ
- EB-004 - Application Enumeration โ
- EB-005 - Register URI Protocol Handlers Enumeration โ
- EB-006 - Malicious Browser Addons Installations โ
- EB-007 - Front-End Interface Crash โ
- EB-008 - Windows Shell Environment Manipulation โ
- EB-009 - Binary Planting โ
- EB-010 - Bypass Software Restriction Policies โ
- EB-011 - Bypass Local Group Policies โ
- EB-012 - Privilege Escalation โ
- EB-013 - Memory dump Analysis โ
- EB-014 - Bypass AppLocker Rules โ
๐ Use These Checklists Responsibly: Authorization is MANDATORY
Attack techniques are powerful - use them ethically and legally.
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
โญ Star this repo if you find it useful! โญ
๐ Source: Checklists/Environment-Breakout-Checklist.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Checklists
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics