SRG-OS-000120-ESXI5 - The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm.

Information

Systems must employ cryptographic hashes for passwords using the SHA-2 family of algorithms or FIPS 140-2 approved successors. The use of unapproved algorithms may result in weak password hashes more vulnerable to compromise.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Temporarily disable Lockdown Mode and enable the ESXi Shell via the vSphere Client. Open the vSphere/VMware Infrastructure (VI) Client and log in with appropriate credentials. If connecting to vCenter Server, click on the desired host. Click the Configuration tab. Click Software, Security Profile, Services, Properties, ESXi Shell and Options, respectively. Start the ESXi Shell service, where/as required.
As root, log in to the host and verify the expected setting is configured in the /etc/pam.d/passwd file. The entry format will look similar to 'password sufficient /lib/security/$ISA/pam_unix.so use_authtok nullok shadow'. Edit the file and replace the existing hash key ( md5, des, or sha256) with sha512 or append sha512, if there is no existing key. For example: 'password sufficient /lib/security/$ISA/pam_unix.so use_authtok nullok shadow sha512'.

Re-enable Lockdown Mode on the host.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_ESXi5_Server_V2R1_STIG.zip

Item Details

Category: IDENTIFICATION AND AUTHENTICATION

References: 800-53|IA-7, CAT|II, CCI|CCI-000803, Group-ID|V-39260, Rule-ID|SV-250632r798895_rule, STIG-ID|SRG-OS-000120-ESXI5, STIG-Legacy|SV-51076, STIG-Legacy|V-39260, Vuln-ID|V-250632

Plugin: VMware

Control ID: 99afcd5b852d0122ceeb8edcb6d6d6d4a6f631ff6ffd955e73615df350470e97