VAMI must force clients to select the most secure cipher.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
---|---|---|---|---|---|---|
medium | V-256669 | SRG-APP-000516-WSR-000174 | VCLD-70-000025 | SV-256669r888529_rule | 2023-06-15 | 1 |
Description |
---|
During a Transport Layer Security (TLS) session negotiation, when choosing a cipher during a handshake, normally the client's preference is used. This is potentially problematic as a malicious, dated, or poorly configured client could select the most insecure cipher offered by the server, even if it supports stronger ones. If "ssl.honor-cipher-order" is enabled, the "ssl.cipher-list" setting will be treated as an ordered list of cipher values from most preferred to least, left to right. |
ℹ️ Check |
---|
At the command prompt, run the following command: # /opt/vmware/sbin/vami-lighttpd -p -f /opt/vmware/etc/lighttpd/lighttpd.conf 2>/dev/null|grep "ssl\.honor-cipher-order"|sed 's: ::g' Expected result: ssl.honor-cipher-order = "enable" If the output does not match the expected result, this is a finding. Note: The command must be run from a bash shell and not from a shell generated by the "appliance shell". Use the "chsh" command to change the shell for the account to "/bin/bash". Refer to KB Article 2100508 for more details: https://kb.vmware.com/s/article/2100508 |
✔️ Fix |
---|
Navigate to and open: /opt/vmware/etc/lighttpd/lighttpd.conf Add or reconfigure the following setting: ssl.honor-cipher-order = "enable" Restart the service with the following command: # vmon-cli --restart applmgmt |