Reserved UIDs 0-99 must only be used by system accounts.

From Solaris 11 SPARC Security Technical Implementation Guide

Associated with: CCI-000366

SV-60949r3_rule Reserved UIDs 0-99 must only be used by system accounts.

Vulnerability discussion

If a user is assigned a UID that is in the reserved range, even if it is not presently in use, security exposures can arise if a subsequently installed application uses the same UID.

Check content

The root role is required. Check that reserved UIDs are not assigned to non-system users. # logins -so | awk -F: '{ print $1 }' | while read user; do found=0 for tUser in adm aiuser bin daemon dhcpserv dladm ftp \ gdm listen lp mysql netadm netcfg noaccess \ nobody nobody4 nuucp openldap pkg5srv postgres \ root smmsp svctag sys unknown uucp upnp \ ikeuser webservd xvm zfssnap sshd; do if [ ${user} = ${tUser} ]; then found=1 fi done if [ $found -eq 0 ]; then echo "Invalid User with Reserved UID: ${user}" fi done If output is produced, this is a finding.

Fix text

The root role is required. Correct or justify any items discovered in the Check step. Determine if there are any accounts using these reserved UIDs, and work with their owners to determine the best course of action in accordance with site policy. This may require deleting users or changing UIDs for users.

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.