← Back to Red Hat Enterprise Linux 10 Security Technical Implementation Guide

V-281233

CAT II (Medium)

RHEL 10 must prevent files with the "setuid" and "setgid" bit set from being executed on the "/boot" directory.

Rule ID

SV-281233r1166651_rule

STIG

Red Hat Enterprise Linux 10 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-001764

Discussion

The "nosuid" mount option causes the system not to execute "setuid" and "setgid" files with owner privileges. This option must be used for mounting any file system not containing approved "setuid" and "setguid" files. Executing files from untrusted file systems increases the opportunity for nonprivileged users to attain unauthorized administrative access.

Check Content

Verify RHEL 10 is configured so that the "/boot" directory is mounted with the "nosuid" option with the following command:

$ mount | grep '\s/boot\s'
/dev/sda1 on /boot type xfs (rw,nodev,nosuid,relatime,seclabel,attr2)

If the "/boot" file system does not have the "nosuid" option set, this is a finding.

Fix Text

Configure RHEL 10 to prevent files with the "setuid" and "setgid" bit set from being executed on the "/boot" directory.

Modify "/etc/fstab" to use the "nosuid" option on the "/boot" directory.

To reload all implicit mount units and update the dependency graph so that new options will apply correctly at next remount, run the following command:

$ sudo systemctl daemon-reload

Use the following command to apply the changes immediately without a reboot:

$ sudo mount -o remount /boot