Skip to content

v2.7.15

Latest

Choose a tag to compare

@github-actions github-actions released this 17 Nov 07:42

Container runs that cannot reach the host filesystem are no longer blocked for file deletions that only take effect inside the container.

Fixed

  • Fixed docker, podman, and nerdctl run commands being blocked by local-filesystem rules such as rm.git-metadata when the container has no way to reach the host, so an idiom like docker run --rm -w /tmp/app alpine sh -c 'rm -rf .git' now runs. (#366)
    • The container counts as isolated only when every -v, --volume, and --mount is read-only and the run carries none of --volumes-from, --privileged, --pid, --userns, --device, --rootfs, --cap-add, a .sock mount, or a /run or /var/run mount.
    • Protections are unchanged everywhere else: writable mounts, docker exec, unknown options before run, and words that could hide an option still get the full scan; git.push-*, network.*, and interpreter.* rules still block inside an isolated payload; and the strict safety level, any custom rule naming a command in the payload, and an enabled rm.recursive-force-paranoid or interpreter.one-liner-paranoid rule all keep every previous verdict.