Details

The rhttpproxy client connections must be limited to preserve system resources and continue servicing connections without interruption. Without a limit set, the system would be vulnerable to a trivial denial-of-service attack where connections are created en masse and vCenter resources are entirely consumed. The rhttproxy comes configured with a tested and supported value that must be maintained.

Solution

Navigate to and open /etc/vmware-rhttpproxy/config.xml.

Locate the // block and configure as follows:

2048

Restart the service for changes to take effect.

# vmon-cli –restart rhttpproxy

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_6-7_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Access Control.This control applies to the following type of system Unix.

References

• 800-53|AC-10
• CAT|II
• CCI|CCI-000054
• Rule-ID|SV-240717r679664_rule
• STIG-ID|VCRP-67-000002
• Vuln-ID|V-240717

Source

• Tenable.com/audits