đź§ Windows Kiosk - Breakout
What is it?
- Concept: Escaping a locked-down Windows Kiosk session (Assigned Access / Shell Launcher) where a single app has replaced
explorer.exeand key filters block the usual shortcuts, to reach arbitrary command execution as the kiosk user. - Impact: Interactive shell (often the foothold/user) from what looks like a dead-end single-purpose terminal.
How it works
- In kiosk mode the only barrier is the shell-replacement app + key filters. There is no taskbar/Start menu, and
Win,Alt+Tab,Ctrl+Escare usually filtered. - The escape is to get any other process to spawn on top of the kiosk app — a dialog, a hyperlink, a file picker, a print/help window — then use that process’s own capabilities to launch a shell.
- A File Open/Save dialog or a browser is the classic pivot: its address/filename box accepts paths and UNC, and a browser’s
Ctrl+Oopens a file dialog from which you can navigate to and launchcmd.exe.
Exploitation
Prerequisites
- An interactive kiosk session (RDP or physical)
- The kiosk app exposes some secondary window — an error dialog, a hyperlink, a file/print dialog, or a help window
Attack Vectors
Try whichever secondary window the kiosk app exposes — each spawns or reaches a different process.
Browser child process (strongest)
A hyperlink / “error details” link opens the default browser → Ctrl+O → file dialog → type C:\Windows\System32\cmd.exe → Open.
File Open / Save As dialog
filename box: cmd.exe (or powershell.exe)
address bar: \\127.0.0.1\C$\Windows\System32 (UNC) then right-click -> Open
right-click a file -> "Open with" / "Open containing folder"Print dialog
Ctrl+P → “Microsoft Print to PDF” → its Save dialog → same file-dialog trick.
Help / embedded web views
F1 help windows or in-app web views → follow a link → browser.
Worked example (HTB Touch): the app had no reachable dialog until its backend dependency was broken — disabling the scanner from the device dashboard forced the kiosk app into an error pop-up whose link opened the default browser →
Ctrl+O→C:\Windows\System32\cmd.exe.
Notes
- If the app seems fully locked, attack its backend/dependencies — removing a device/service the app relies on often throws an error dialog, and that dialog is the breakout surface.
- Key filters usually miss app-internal shortcuts (
Ctrl+O,Ctrl+P,Ctrl+S), right-click context menus, and accessibility tools (On-Screen Keyboard, Narrator, Sticky Keys). - Once you have
cmd.exeyou have a shell as the kiosk user — pivot to privesc from there (see Windows - Service Permission Abuse).
Mitigation
- Fix: Harden Assigned Access — remove browsers, disable file/print dialogs and hyperlinks in the kiosk app, enforce AppLocker/WDAC, and strip accessibility launch paths.
Related Usage
| File | Created |
|---|---|
| HTB Machine - Touch | October 07, 2026 |
References: