Add nodev Option to /var/tmp
Mount /var/tmp with the nodev option so device nodes placed there are ignored by the kernel.
Checked against the resolved running state (e.g. sshd -T, sysctl, systemctl show), catches drop-ins and Includes a file read would miss. Caveat: runtime ≠ persistence; a value correct now may not survive a reboot.
Pavois asserts the effective configuration, the live, resolved state, not a file. File-based scanners (OVAL/SCAP, Lynis) miss Includes, drop-ins and runtime defaults; this check sees what is actually applied.
A mapping is a cross-reference to where each standard places this requirement, anchored and cross-validated, not a claim of equivalence. A passing check is evidence toward these references, how to read it.
Why this rule matters
The only legitimate location for device files is /dev on the root partition (chroot jails are the rare exception). Mounting /var/tmp with nodev makes the kernel ignore any character or block device nodes placed there, blocking an attacker from smuggling a device file (e.g. raw disk access) into a world-writable temporary directory.
What Pavois checks
Pavois reads the effective mount options via mount('/var/tmp'). Because /var/tmp is often a bind mount or a systemd-managed tmpfs, the live kernel view is the only reliable source, parsing /etc/fstab alone would miss bind mounts and runtime remounts.
describe mount('/var/tmp') do
its('options') { should include 'nodev' }
end
describe command("{ findmnt --fstab -no OPTIONS /var/tmp 2>/dev/null; grep -hsE '[[:space:]]/var/tmp[[:space:]]' /etc/fstab 2>/dev/null; systemctl show -p Options -- $(systemd-escape -p --suffix=mount /var/tmp 2>/dev/null) 2>/dev/null; } | grep -ow 'nodev'") do
its('stdout') { should match(/\S/) }
endHow to verify it is applied
Run findmnt -no OPTIONS /var/tmp and confirm nodev is present. Example output: rw,nosuid,nodev,noexec,relatime.
Inspect & investigate
Inspect mount state with findmnt /var/tmp and mount | grep ' /var/tmp '. Kernel mount events appear in journalctl -k / dmesg. To spot existing device nodes, run find /var/tmp -type c -o -type b.
Remediation
There is no automated harden plan for this rule, because /var/tmp must be a separate filesystem or bind mount to carry its own options. Apply it manually: configure /var/tmp as its own mount, add nodev to its /etc/fstab entry (or systemd mount unit), then mount -o remount /var/tmp and reboot to confirm persistence.
Pavois applies this with its own harden engine, the plan below, not a shell script:
| command | awk -v m=/var/tmp -v o=nodev '$0!~/^[[:space:]]*#/&&$2==m{n=split($4,a,",");h=0;for(i=1;i<=n;i++)if(a[i]==o)h=1;if(!h)$4=$4","o}{print}' /etc/fstab >/etc/.fstab.pav && cat /etc/.fstab.pav >/etc/fstab && rm -f /etc/.fstab.pav; mountpoint -q /var/tmp && mount -o remount,nodev /var/tmp || true |
|---|---|
| name | mount-var-tmp-nodev |
| not_if | awk -v m=/var/tmp '$2==m&&$0!~/^[[:space:]]*#/{print $4}' /etc/fstab | tr , '\n' | grep -qx nodev |
| resource | exec |
pavois harden plan localwhere the target is local, a user@host SSH alias, or a container , Docs
Impact & precautions
What can break: essentially nothing in normal operation, legitimate workloads never need device nodes under /var/tmp. Precautions: if /var/tmp is not already a separate mount, the main effort is making it one (often a bind mount of /tmp or a dedicated filesystem). Test the remount in staging and reboot to confirm the option survives.
Standards mapping
| Standard | Reference | Type | Version | Confidence |
|---|---|---|---|---|
| CIS | 1.1.2.5.2 | direct | per OS, see the benchmark table | high |
Each reference is a cross-reference anchored in the upstream benchmark and cross-validated against the SCAP Security Guide and ansible-lockdown, not a claim of equivalence. Direct = a prescriptive, line-level requirement; supporting = an abstract control family (NIST) the check provides evidence toward. How to read a mapping.