Envoy must set a limit on established connections.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-256738 | VCRP-70-000002 | SV-256738r889152_rule | CCI-000054 | medium |
| Description | ||||
| Envoy 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. Envoy comes hard coded with a tested and supported value for "maxHttpsConnections" that must be verified and maintained. | ||||
| STIG | Date | |||
| VMware vSphere 7.0 vCenter Appliance RhttpProxy Security Technical Implementation Guide | 2023-02-21 | |||
Details
Check Text (C-256738r889152_chk)
At the command prompt, run the following command:
# xmllint --xpath '/config/envoy/L4Filter/maxHttpsConnections/text()' /etc/vmware-rhttpproxy/config.xml
Expected result:
2048
or
XPath set is empty
If the output does not match the expected result, this is a finding.
Fix Text (F-60356r889151_fix)
Navigate to and open:
/etc/vmware-rhttpproxy/config.xml
Locate the <config>/<envoy>/<L4Filter> block and configure <maxHttpsConnections> as follows:
<maxHttpsConnections>2048</maxHttpsConnections>
Restart the service for changes to take effect.
# vmon-cli --restart rhttpproxy