The vCenter Lookup service must limit the number of maximum concurrent connections permitted.

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.

Satisfies: SRG-APP-000001-AS-000001, SRG-APP-000435-AS-000163

At the command prompt, run the following command:

# xmllint --xpath '/Server/Service/Executor[@name="tomcatThreadPool"]/@maxThreads' /usr/lib/vmware-lookupsvc/conf/server.xml

Expected result:

maxThreads="300"

If the output does not match the expected result, this is a finding.

Navigate to and open:

/usr/lib/vmware-lookupsvc/conf/server.xml

Navigate to the <Executor> node with the name of tomcatThreadPool and configure with the value "maxThreads="300"".

Note: The <Executor> node should be configured similar to the following:

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

Restart the service with the following command:

# vmon-cli --restart lookupsvc