Sandboxing


System Security.

Computer security sandboxing refers to a technique used to isolate potentially malicious code or untrusted programs, ensuring they run in a confined environment where they cannot cause harm to the broader system. By creating a 'sandbox' or restricted space for these programs to operate in, any malicious actions are confined to this isolated area, preventing potential damage to the host system or access to sensitive data. This module explores sandboxing techniques as well as how hackers can escape a misconfigured sandbox.



Filesystem Sandboxing

Escape a basic chroot sandbox!

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a basic chroot sandbox by utilizing shellcode.

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox with shellcode.

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

System Call Sandboxing

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["openat", "read", "write", "sendfile"]

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["linkat", "open", "read", "write", "sendfile"]

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["fchdir", "open", "read", "write", "sendfile"]

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["chdir", "chroot", "mkdir", "open", "read", "write", "sendfile"]

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["openat", "read", "write", "sendfile"]

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["close", "stat", "fstat", "lstat"]

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["read", "exit"]. Note that "write" is disabled! You will need a creative way of extracting the flag data from your process!

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["read", "nanosleep"]. Note that "write" is disabled! You will need a creative way of extracting the flag data from your process!

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a chroot sandbox using shellcode, but this time only using the following syscalls: ["read"]. Note that "write" is disabled! You will need a creative way of extracting the flag data from your process!

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Escape a different kind of sandbox in which a jailed child process is only communicable to from a parent process.

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Sandboxing via Namespaces

Learn the implications of a different way of sandboxing, using modern namespacing techniques! But what if the sandbox is really sloppy?

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Learn the implications of a different way of sandboxing, using modern namespacing techniques! But what are the implications of sharing filesystems between the sandbox and host?

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Learn the implications of a different way of sandboxing, using modern namespacing techniques! But what shenanigans can you get up to with special kernel-backed filesystems?

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Learn the implications of a different way of sandboxing, using modern namespacing techniques! But what happens if you can smuggle in a resource from the outside?

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

Learn the implications of a different way of sandboxing, using modern namespacing techniques! What could be the harm of mounting in a harmless directory?

Connect with SSH

Link your SSH key, then connect with: ssh [email protected]

30-Day Scoreboard:

This scoreboard reflects solves for challenges in this module after the module launched in this dojo.

7-Day | 30-Day | All-Time

Rank Hacker Badges Score