Title

All local initialization files must be owned by the user or root. (Cat II impact)

Discussion

Local initialization files are used to configure the user's shell environment upon login. Malicious modification of these files could compromise accounts upon logon.

Check Content

Open a terminal session and enter the following commands to verify ownership of local initialization files. ls -al /<usershomedirectory>/.login ls -al /<usershomedirectory>/.cshrc ls -al /<usershomedirectory>/.logout ls -al /<usershomedirectory>/.profile ls -al /<usershomedirectory>/.bash_profile ls -al /<usershomedirectory>/.bashrc ls -al /<usershomedirectory>/.bash_logout ls -al /<usershomedirectory>/.env ls -al /<usershomedirectory>/.dtprofile ls -al /<usershomedirectory>/.dispatch ls -al /<usershomedirectory>/.emacs ls -al /<usershomedirectory>/.exrc find /<usershomedirectory>/.dt ! -fstype nfs ! -user <username> -exec ls -ld {} \; If local initialization files are not owned by the home directory's user or root, this is a finding.

Fix Text

Open a terminal session and enter the following command to change the ownership of the start-up and login files in the user’s directory to the user or root, as appropriate. Examine each user’s home directory and verify all filenames beginning with "." are owned by the owner of the directory or root. If they are not, use the chown command to change the owner to the user and research the reasons why the owners were not assigned as required. chown <username> </directory/filename>

Additional Identifiers

Rule ID: SV-38010r1_rule

Vulnerability ID: V-904

Group Title:

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.