sandbox-app-launcher - Sandboxed Application Launcher

From Kicksecure
Jump to navigation Jump to search

sandbox-app-launcher is an application launcher that starts each app inside its own restrictive sandbox. It runs each app as its own user, in a bubblewrap sandbox and confined by AppArmor.

Developers only! Warning: This is for developers-only!

Introduction[edit]

sandbox-app-launcher is an application launcher that can start each application inside its own restrictive sandbox. It runs each application as its own user, within a bubblewrap sandbox and confined by AppArmor.

This launcher is geared towards end-user applications, not any system software. The directory /shared is shared across all application sandboxes to transfer files across.

This implements a permissions system to configure what applications can access. There are currently five available permissions:

  • network access;
  • webcam access;
  • microphone access;
  • shared storage access (read-only or read-write); and
  • dynamic native code execution.

All user-installed applications will be automatically configured to run in the sandbox and a prompt will ask which permissions should be granted to the application (not implemented yet).

The launcher is currently a work-in-progress and is not yet ready for actual use. To learn more, see:

Design[edit]

Bubblewrap allows developers to make use of namespacesarchive.org and seccomparchive.org. All applications are run in mount, PID, cgroup and UTS namespaces; IPC namespaces are planned but are not currently implemented due to limitations in Xorg. Fine-grained filesystem restrictions are implemented via mount namespaces and AppArmor. Seccomp blocks certain syscalls which can greatly reduce kernel attack surface among other things.

All applications by default use a seccomp whitelist to block dangerous and unused syscallsarchive.org. In addition, the arguments of some syscalls are filtered to:

  • Block unused socket address familiesarchive.org.
  • Block any dangerous or unused ioctlsarchive.org such as TIOCSTI (can be used in sandbox escapes), TIOCSETD (can increase kernel attack surface by loading vulnerable line disciplines), SIOCGIFHWADDR (can retrieve the user’s MAC address), etc.
  • Implement W^Xarchive.org (explained in detail further below).

Apparmor also gives fine-grained controls over IPC signals, D-Bus, UNIX sockets, ptrace and more.

Sandbox Escape Mitigation[edit]

Table: Sandboxed Application Launcher Mitigations

Sandbox Escape Vector Mitigation
D-Bus D-Busarchive.org is common avenue for sandbox escapes. [1] This attack vector is mitigated by denying access to the system bus and only allowing access to the session bus. This is safe since each application runs as their own user with their own session bus, ensuring no IPCarchive.org between sandboxes.
Dynamic Native Code Execution Dynamic native code execution is generally a security issue since it allows an attacker to execute new arbitrary code. This is prevented by the following mechanisms:
  • Enforcing strict W^X in both memory and the filesystem.
  • Seccomp is used to prevent creation of memory mappings that are both writable and executable and transitioning a writable memory mapping to executable.
  • AppArmor is used to prevent execution of programs from writable directories.

These mechanisms force attackers to utilize the already existing code (e.g. Return-oriented programming (ROP)archive.org / Jump-Oriented-Programming (JOP)archive.org) which is much more limited and difficult. The main things that legitimately require this are JIT engines in browsers.

Malware Persistence The only places malware can persist inside the sandbox are the home directory or shared storage (if enabled as read-write) and it can only ever be executed if W^X is disabled. Everything else is mounted read-only or as a tmpfsarchive.org (a file system which keeps all files in virtual memory).
PulseAudio PulseAudioarchive.org was also not written with isolation in mind [2] so access to it is blacklisted from within the sandbox. By default this will break a lot of things so a more robust solution like PipeWirearchive.org may be used in the future.
Separate User per Sandboxed Application This approach provides a higher security threshold: [3]

Sandboxing programs running as the same user has historically, never seriously worked well. It’s been the cause of many issues with e.g. Flatpak. It’s why Android/iOS have always used separate users.

X11 X11archive.org does not have GUI isolation [4] so it is trivial to escape sandboxes with it. There is no protection against this vector at present, but the plan is to either switch to Wayland [5] or use a nested X11 server like Xpra.

Installation[edit]

Install sandbox-app-launcher. To accomplish that, the following steps A. to D. need to be done.

A. Update the package lists.

sudo apt update

B. Upgrade the system.

sudo apt full-upgrade

C. Install the sandbox-app-launcher package.

Using apt command line parameter --no-install-recommends is in most cases optional.

sudo apt install --no-install-recommends sandbox-app-launcher

D. Done.

The procedure of installing sandbox-app-launcher is complete.

Usage[edit]

Setup[edit]

For example, to setup a sandbox for firefox, run.

sudo sandbox-app-launcher setup firefox

Use[edit]

For example, to start firefox using sandbox-app-launcher, run.

sandbox-app-launcher start firefox

To show all sand boxes.

sandbox-app-launcher list

To delete user data.

sudo sandbox-app-launcher remove firefox

Development Discussion[edit]

https://forums.whonix.org/t/system-wide-sandboxing-framework-sandbox-app-launcher/9008archive.org

References[edit]


Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 11 year success story and maybe DONATE!