Crontab files must not have extended ACLs.

From SUSE Linux Enterprise Server v11 for System z Security Technical Implementation Guide

Associated with: CCI-000225

SV-45601r1_rule Crontab files must not have extended ACLs.

Vulnerability discussion

To protect the integrity of scheduled system jobs and to prevent malicious modification to these jobs, crontab files must be secured. ACLs on crontab files may provide unauthorized access to the files.

Check content

Check the permissions of the crontab files. Procedure: # ls -lL /var/spool/cron /var/spool/cron/tabs ls –lL /etc/crontab /etc/cron.{d,daily,hourly,monthly,weekly} or # ls -lL /etc/cron*|grep -v deny If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.

Fix text

Remove the extended ACL from the file. # setfacl --remove-all [crontab file]

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.