Check: VCEM-67-000002
VMware vSphere 6.7 EAM Tomcat STIG:
VCEM-67-000002
(in versions v1 r4 through v1 r1)
Title
ESX Agent Manager must limit the number of concurrent connections permitted. (Cat II impact)
Discussion
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.
Check Content
At the command prompt, execute the following command: # xmllint --xpath '/Server/Service/Executor[@name="tomcatThreadPool"]/@maxThreads' /usr/lib/vmware-eam/web/conf/server.xml Expected result: maxThreads="300" If the output does not match the expected result, this is a finding.
Fix Text
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--"/>
Additional Identifiers
Rule ID: SV-239373r879511_rule
Vulnerability ID: V-239373
Group Title: SRG-APP-000001-WSR-000001
Expert Comments
CCIs
Number | Definition |
---|---|
CCI-000054 |
The information system limits the number of concurrent sessions for each organization-defined account and/or account type to an organization-defined number of sessions. |
Controls
Number | Title |
---|---|
AC-10 |
Concurrent Session Control |