TMA-DOCKER-3.24

Ensure that the Containerd socket file permissions are set to 660 or more restrictively

HighLevel 1Automateddocker

Description

The containerd socket /run/containerd/containerd.sock must have mode 660 or more restrictive so that it cannot be modified by non-root users. The audit flags any existing candidate path (/run/containerd/containerd.sock) with permission bits outside 660; not applicable when none exists.

How it is checked

Audit method: Shell command

shell

for f in /run/containerd/containerd.sock; do [ -e "$f" ] || continue; out=$(find "$f" -maxdepth 0 -perm /7117) || exit 1; [ -z "$out" ] || { echo "$f"; exit 0; }; done; echo compliant

Expected output: compliant

How it is fixed

Fix method: Shell command

shell

for f in /run/containerd/containerd.sock; do if [ -e "$f" ]; then chmod 660 "$f" || exit 1; fi; done

Properties

Operating systems: Any
Tags: dockerpermissions
Reference: CIS Docker Benchmark v1.9.0 - 3.24 Ensure that the Containerd socket file permissions are set to 660 or more restrictively

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target docker