VCEM-67-000002 - ESX Agent Manager must limit the number of concurrent connections permitted.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Resource exhaustion can occur when an unlimited number of concurrent requests are allowed on a website, facilitating a denial-of-service attack. Unless the number of requests is controlled, the web server can consume enough system resources to cause a system crash.

Mitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests. In Tomcat, each incoming request requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the value of the maxThreads attribute.

Solution

Navigate to and open:

/usr/lib/vmware-eam/web/conf/server.xml

Navigate to the <Executor> mode with the name of tomcatThreadPool and configure with the value 'maxThreads='300''

Note: The <Executor> node should be configured as follows:

<Executor maxThreads='300'
minSpareThreads='50'
name='tomcatThreadPool'
namePrefix='tomcat-http--'/>

See Also

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

Item Details

References: CAT|II, CCI|CCI-000054, Rule-ID|SV-239373r674613_rule, STIG-ID|VCEM-67-000002, Vuln-ID|V-239373

Plugin: Unix

Control ID: df227d36788c4c80fc63424e7c02a51abea6555258a547a3d99c49f1d049967c