Bug ID 428993: Account must not have blank or null passwords

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.4.0, 11.4.1

Fixed In:
11.5.0

Opened: Aug 27, 2013
Severity: 2-Critical

Symptoms

STIG Group ID (Vulid): V-38497 Group Title: SRG-OS-999999 Rule ID: SV-50298r1_rule Severity: CAT I --------- RHEL SCAP: CCE-27038-9 --------- If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.

Impact

If an account has an empty password, anyone could log in and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.

Conditions

nullok option in /etc/pam.d/system-auth

Workaround

Remove any instances of the nullok option in /etc/pam.d/system-auth to prevent logins with empty passwords.

Fix Information

If an account is configured for password authentication but does not have an assigned password, it may be possible to log into the account without authentication. Remove any instances of the "nullok" option in "/etc/pam.d/system-auth-ac" to prevent logins with empty passwords.

Behavior Change

No empty passwords will be allowed.