Skip to content

Security: alexghirelli/airlock

Security

SECURITY.md

Security policy

airlock's purpose is containment, so reports about ways out of the sandbox are welcome, especially:

  • reaching the host, the local network or cloud metadata from inside a sandbox;
  • changing the firewall or regaining dropped capabilities from inside;
  • writing to paths that should be read-only (.git/hooks, .git/config, mounts declared ro);
  • a project's .airlock.toml taking effect beyond its allowed keys;
  • credentials or tokens leaking between sandboxes or to the host.
  • the host running a program that a sandbox wrote into a repository (through git's own discovery, a commondir or a worktree's .git file, or config and attributes it can reach): airlock summary, wt, remote and review must run git only through internal/hostgit.

Please report privately to the repository owner rather than opening a public issue, and include the airlock version, the engine (Docker version, rootless or not, OS) and the smallest steps to reproduce. There is no bug bounty.

Known limits, such as the shared host kernel of the container backend, are listed under "What it does not protect against" in the README and are not vulnerabilities.

There aren't any published security advisories