Cause: File permissions on configuration file weren't too strict.
Consequence: Every user can read many configuration files of cron.
Fix: File permissions were changed.
Result: Only root can read the configuration files.
Description of problem:
The DISA STIG calls out for cron config files to be 0600 or more restrictive:
Currently there are files that have 0644 permissions. We need to align the permissions to match the STIG so there is less to lockdown out of the box.
I can't be responsible for scripts in cron directories /etc/crond.*, because there are created by other applications or users. They are executable on purpose in some cases.
Also please note -p option, which is used for crontabs in /var/spool/cron directory. Crontabs there should be according to your policy.
crontab files have to be regular files or symlinks to regular files, they must not be executable or writable for anyone else but the owner. This requirement can be overridden by using the -p option on the crond command line. If inotify support is in use, changes in the symlinked crontabs are not automatically noticed by the cron daemon.
Config files can be changed to 600 if they have higher permission.
There is a script here that can be used for testing:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.