Vulnerability Discussion

The organization must identify authorized software programs and permit execution of authorized software. The process used to identify software programs that are authorized to execute on organizational information systems is commonly referred to as whitelisting.

The "noexec" mount option causes the system to not execute binary files. This option must be used for mounting any file system not containing approved binary files, as they may be incompatible. Executing files from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.

The "nodev" mount option causes the system to not interpret character or block special devices. Executing character or block special devices from untrusted file systems increases the opportunity for unprivileged users to attain unauthorized administrative access.

The "nosuid" mount option causes the system to not 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 unprivileged users to attain unauthorized administrative access.

Check

Verify "/tmp" is mounted with the "noexec" option:

$ sudo mount | grep /tmp

/dev/mapper/ol-tmp on /tmp type xfs (rw,nodev,nosuid,noexec,seclabel)

Verify that the "noexec" option is configured for /tmp:

$ sudo cat /etc/fstab | grep /tmp

/dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0

If results are returned and the "noexec" option is missing, or if /tmp is mounted without the "noexec" option, this is a finding.

Fix

Configure the system so that /tmp is mounted with the "noexec" option by adding /modifying the /etc/fstab with the following line:

/dev/mapper/ol-tmp /tmp xfs defaults,nodev,nosuid,noexec 0 0