None Computing title VMware vSphere 7.0 vCenter Appliance EAM Security Technical Implementation Guide version 1 releaseinfo Release: 2 Vuln_Num V-256673 Rule_ID SV-256673r888575_rule Severity medium Rule_Title ESX Agent Manager must limit the amount of time that each Transmission Control Protocol (TCP) connection is kept alive. Vuln_Discuss Denial of service (DoS) is one threat against web servers. Many DoS attacks attempt to consume web server resources in such a way that no more resources are available to satisfy legitimate requests. In Tomcat, the "connectionTimeout" attribute sets the number of milliseconds the server will wait after accepting a connection for the request Uniform Resource Identifier (URI) line to be presented. This timeout will also be used when reading the request body (if any). This prevents idle sockets that are not sending HTTP requests from consuming system resources and potentially denying new connections. Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Connector/@connectionTimeout' /usr/lib/vmware-eam/web/conf/server.xml Expected result: connectionTimeout="60000" 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 Configure the <Connector> node with the value: connectionTimeout="60000" Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256674 Rule_ID SV-256674r888578_rule Severity medium Rule_Title ESX Agent Manager must limit the number of concurrent connections permitted. Vuln_Discuss 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, run 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--"/> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256675 Rule_ID SV-256675r888581_rule Severity medium Rule_Title ESX Agent Manager must limit the maximum size of a POST request. Vuln_Discuss The "maxPostSize" value is the maximum size in bytes of the POST that will be handled by the container FORM URL parameter parsing. Limit its size to reduce exposure to a denial-of-service attack. If "maxPostSize" is not set, the default value of 2097152 (2MB) is used. ESX Agent Manager is configured in its shipping state to not set a value for "maxPostSize". Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Connector/@maxPostSize' /usr/lib/vmware-eam/web/conf/server.xml Expected result: XPath set is empty 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 Remove any configuration for "maxPostSize" from the <Connector> node. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256676 Rule_ID SV-256676r888584_rule Severity medium Rule_Title ESX Agent Manager must protect cookies from cross-site scripting (XSS). Vuln_Discuss Cookies are a common way to save session state over the HTTP(S) protocol. If attackers can compromise session data stored in a cookie, they are better able to launch an attack against the server and its applications. When a cookie is tagged with the "HttpOnly" flag, it tells the browser this particular cookie should only be accessed by the originating server. Any attempt to access the cookie from client script is strictly forbidden. Satisfies: SRG-APP-000001-WSR-000002, SRG-APP-000223-WSR-000011, SRG-APP-000439-WSR-000154, SRG-APP-000439-WSR-000155 Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/session-config/cookie-config/http-only' - Expected result: <http-only>true</http-only> If the output does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Navigate to the <session-config> node and configure it as follows: <session-config> <cookie-config> <http-only>true</http-only> <secure>true</secure> </cookie-config> <session-timeout>30</session-timeout> </session-config> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256677 Rule_ID SV-256677r888587_rule Severity medium Rule_Title ESX Agent Manager must record user access in a format that enables monitoring of remote access. Vuln_Discuss Remote access can be exploited by an attacker to compromise the server. By recording all remote access activities, it will be possible to determine the attacker's location, intent, and degree of success. Tomcat can be configured with an "AccessLogValve", a component that can be inserted into the request processing pipeline to provide robust access logging. The "AccessLogValve" creates log files in the same format as those created by standard web servers. When "AccessLogValve" is properly configured, log files will contain all the forensic information necessary in the case of a security incident. Satisfies: SRG-APP-000016-WSR-000005, SRG-APP-000089-WSR-000047, SRG-APP-000092-WSR-000055, SRG-APP-000093-WSR-000053, SRG-APP-000095-WSR-000056, SRG-APP-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000098-WSR-000059, SRG-APP-000098-WSR-000060, SRG-APP-000099-WSR-000061, SRG-APP-000100-WSR-000064, SRG-APP-000375-WSR-000171, SRG-APP-000374-WSR-000172 Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Engine/Host/Valve[@className="org.apache.catalina.valves.AccessLogValve"]/@pattern' /usr/lib/vmware-eam/web/conf/server.xml Expected result: pattern="%h %{X-Forwarded-For}i %l %u %t [%I] "%r" %s %b [Processing time %D msec] "%{User-Agent}i"" 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 Inside the <Host> node, find the "AccessLogValve" <Valve> node and replace the "pattern" element as follows: pattern="%h %{X-Forwarded-For}i %l %u %t [%I] "%r" %s %b [Processing time %D msec] "%{User-Agent}i"" Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256678 Rule_ID SV-256678r888590_rule Severity medium Rule_Title ESX Agent Manager must generate log records for system startup and shutdown. Vuln_Discuss Logging must be started as soon as possible when a service starts and as late as possible when a service is stopped. Many forms of suspicious actions can be detected by analyzing logs for unexpected service starts and stops. Also, by starting to log immediately after a service starts, it becomes more difficult for suspicious activity to go unlogged. Check_Content At the command prompt, run the following command: # grep StreamRedirectFile /etc/vmware/vmware-vmon/svcCfgfiles/eam.json Expected output: "StreamRedirectFile" : "%VMWARE_LOG_DIR%/vmware/eam/jvm.log", If no log file is specified for the "StreamRedirectFile" setting, this is a finding. Fix_Text Navigate to and open: /etc/vmware/vmware-vmon/svcCfgfiles/eam.json Below the last line of the "PreStartCommandArg" block, add the following line: "StreamRedirectFile" : "%VMWARE_LOG_DIR%/vmware/eam/jvm.log", Restart the appliance for changes to take effect. Not_Reviewed Vuln_Num V-256679 Rule_ID SV-256679r888593_rule Severity medium Rule_Title ESX Agent Manager log files must only be modifiable by privileged users. Vuln_Discuss Log data is essential in the investigation of events. The accuracy of the information is always pertinent. One of the first steps an attacker will take is the modification or deletion of log records to cover tracks and prolong discovery. The web server must protect the log data from unauthorized modification. ESX Agent Manager restricts all modification of log files by default, but this configuration must be verified. Satisfies: SRG-APP-000119-WSR-000069, SRG-APP-000120-WSR-000070 Check_Content At the command prompt, run the following command: # find /var/log/vmware/eam/web/ -xdev -type f -a '(' -perm -o+w -o -not -user eam -o -not -group users ')' -exec ls -ld {} \; If any files are returned, this is a finding. Fix_Text At the command prompt, run the following commands: # chmod o-w <file> # chown eam:users <file> Note: Substitute <file> with the listed file. Not_Reviewed Vuln_Num V-256680 Rule_ID SV-256680r918904_rule Severity medium Rule_Title ESX Agent Manager application files must be verified for their integrity. Vuln_Discuss Verifying that ESX Agent Manager application code is unchanged from its shipping state is essential for file validation and nonrepudiation of the ESX Agent Manager. There is no reason the MD5 hash of the RPM original files should be changed after installation, excluding configuration files. Satisfies: SRG-APP-000131-WSR-000051, SRG-APP-000357-WSR-000150 Check_Content At the command prompt, run the following command: # rpm -V vmware-eam|grep "^..5......" | grep -v 'c /' | grep -v -E ".installer|.properties|.xml" If there is any output, this is a finding. Fix_Text Reinstall the vCenter Server Appliance (VCSA) or roll back to a backup. Modifying the EAM installation files manually is not supported by VMware. Not_Reviewed Vuln_Num V-256681 Rule_ID SV-256681r888599_rule Severity medium Rule_Title ESX Agent Manager must only run one webapp. Vuln_Discuss VMware ships ESX Agent Managers on the vCenter Server Appliance (VCSA) with one webapp. Any other path is potentially malicious and must be removed. Satisfies: SRG-APP-000131-WSR-000073, SRG-APP-000141-WSR-000075 Check_Content At the command prompt, run the following command: # ls -A /usr/lib/vmware-eam/web/webapps Expected result: eam If the output does not match the expected result, this is a finding. Fix_Text For each unexpected directory returned in the check, run the following command: # rm /usr/lib/vmware-eam/web/webapps/<NAME> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256682 Rule_ID SV-256682r888602_rule Severity medium Rule_Title ESX Agent Manager must not be configured with unsupported realms. Vuln_Discuss ESX Agent Manager performs authentication at the application level and not through Tomcat. To eliminate unnecessary features and ensure ESX Agent Manager remains in its shipping state, the lack of a "UserDatabaseRealm" configuration must be confirmed. Check_Content At the command prompt, run the following command: # grep UserDatabaseRealm /usr/lib/vmware-eam/web/conf/server.xml If the command produces any output, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/conf/server.xml Remove the <Realm> node returned in the check. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256683 Rule_ID SV-256683r888605_rule Severity medium Rule_Title ESX Agent Manager must be configured to limit access to internal packages. Vuln_Discuss The "package.access" entry in the "catalina.properties" file implements access control at the package level. When properly configured, a Security Exception will be reported if an errant or malicious webapp attempts to access the listed internal classes directly or if a new class is defined under the protected packages. The ESX Agent Manager comes preconfigured with the appropriate packages defined in "package.access", and this configuration must be maintained. Check_Content At the command prompt, run the following command: # grep "package.access" -A 5 /etc/vmware-eam/catalina.properties Expected result: package.access=\ sun.,\ org.apache.catalina.,\ org.apache.coyote.,\ org.apache.tomcat.,\ org.apache.jasper. If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /etc/vmware-eam/catalina.properties Ensure the "package.access" line is configured as follows: package.access=\ sun.,\ org.apache.catalina.,\ org.apache.coyote.,\ org.apache.tomcat.,\ org.apache.jasper. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256684 Rule_ID SV-256684r888608_rule Severity medium Rule_Title ESX Agent Manager must have Multipurpose Internet Mail Extensions (MIMEs) that invoke operating system shell programs disabled. Vuln_Discuss MIME mappings tell ESX Agent Manager what type of program various file types and extensions are and what external utilities or programs are needed to execute the file type. By ensuring various shell script MIME types are not included in "web.xml", the server is protected against malicious users tricking the server into executing shell command files. Check_Content At the command prompt, run the following command: # grep -En '(x-csh<)|(x-sh<)|(x-shar<)|(x-ksh<)' /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml If the command produces any output, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Remove all of the following nodes lines: <mime-type>application/x-csh</mime-type> <mime-type>application/x-shar</mime-type> <mime-type>application/x-sh</mime-type> <mime-type>application/x-ksh</mime-type> Restart the service with the following command: # vmon-cli --restart eam Note: Delete the entire mime-mapping node for the target mime-type. Example: <mime-mapping> <extension>sh</extension> <mime-type>application/x-sh</mime-type> </mime-mapping> Not_Reviewed Vuln_Num V-256685 Rule_ID SV-256685r888611_rule Severity medium Rule_Title ESX Agent Manager must have mappings set for Java servlet pages. Vuln_Discuss Resource mapping is the process of tying a particular file type to a process in the web server that can serve that type of file to a requesting client and identify which file types are not to be delivered to a client. By not specifying which files can and cannot be served to a user, the web server could deliver to a user web server configuration files, log files, password files, etc. Because Tomcat is a Java-based web server, the main file extension used is *.jsp. This check ensures the *.jsp file type has been properly mapped to servlets. Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/servlet-mapping/servlet-name[text()="JspServlet"]/parent::servlet-mapping' - Expected result: <servlet-mapping> <servlet-name>JspServlet</servlet-name> <url-pattern>*.jsp</url-pattern> </servlet-mapping> If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Navigate to and locate the mapping for the JSP servlet. It is the <servlet-mapping> node that contains <servlet-name>JspServlet</servlet-name>. Configure the <servlet-mapping> node to look like the code snippet below: <servlet-mapping> <servlet-name>JspServlet</servlet-name> <url-pattern>*.jsp</url-pattern> </servlet-mapping> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256686 Rule_ID SV-256686r888614_rule Severity medium Rule_Title ESX Agent Manager must not have the Web Distributed Authoring (WebDAV) servlet installed. Vuln_Discuss WebDAV is an extension to the HTTP protocol that, when developed, was meant to allow users to create, change, and move documents on a server, typically a web server or web share. WebDAV is not widely used and has serious security concerns because it may allow clients to modify unauthorized files on the web server and must therefore be disabled. Tomcat uses the "org.apache.catalina.servlets.WebdavServlet" servlet to provide WebDAV services. Because the WebDAV service has been found to have an excessive number of vulnerabilities, this servlet must not be installed. ESX Agent Manager does not configure WebDAV by default. Check_Content At the command prompt, run the following command: # grep -n 'webdav' /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml If the command produces any output, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Find the <servlet-name>webdav</servlet-name> node and remove the entire parent <servlet> block. Find the <servlet-name>webdav</servlet-name> node and remove the entire parent <servlet-mapping> block. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256687 Rule_ID SV-256687r888617_rule Severity medium Rule_Title ESX Agent Manager must be configured with memory leak protection. Vuln_Discuss The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, ESX Agent Manager can continue to consume system resources, which will lead to "OutOfMemoryErrors" when reloading web applications. Memory leaks occur when JRE code uses the context class loader to load a singleton, as this will cause a memory leak if a web application class loader happens to be the context class loader at the time. The "JreMemoryLeakPreventionListener" class is designed to initialize these singletons when Tomcat's common class loader is the context class loader. Proper use of JRE memory leak protection will ensure the hosted application does not consume system resources and cause an unstable environment. Check_Content At the command prompt, run the following command: # grep JreMemoryLeakPreventionListener /usr/lib/vmware-eam/web/conf/server.xml Expected result: <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/> If the output of the command 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 <Server> node. Add '<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>' to the <Server> node. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256688 Rule_ID SV-256688r888620_rule Severity medium Rule_Title ESX Agent Manager must not have any symbolic links in the web content directory tree. Vuln_Discuss A web server is designed to deliver content and execute scripts or applications at the request of a client or user. Containing user requests to files in the directory tree of the hosted web application and limiting the execution of scripts and applications guarantees the user is not accessing information protected outside the application's realm. By checking that no symbolic links exist in the document root, the web server is protected from users jumping outside the hosted application directory tree and gaining access to the other directories, including the system root. Check_Content At the command prompt, run the following command: # find /usr/lib/vmware-eam/web/webapps/ -type l -ls If the command produces any output, this is a finding. Fix_Text At the command prompt, run the following command: Note: Replace <file_name> for the name of any files that were returned. unlink <file_name> Repeat the command for each file that was returned. Not_Reviewed Vuln_Num V-256689 Rule_ID SV-256689r888623_rule Severity medium Rule_Title ESX Agent Manager directory tree must have permissions in an out-of-the-box state. Vuln_Discuss As a rule, accounts on a web server are to be kept to a minimum. Only administrators, web managers, developers, auditors, and web authors require accounts on the machine hosting the web server. The resources to which these accounts have access must also be closely monitored and controlled. ESX Agent Manager files must be adequately protected with correct permissions as applied out of the box. Satisfies: SRG-APP-000211-WSR-000030, SRG-APP-000380-WSR-000072 Check_Content At the command prompt, run the following command: # find /usr/lib/vmware-eam/web/ -xdev -type f -a '(' -not -user root -o -not -group root ')' -exec ls -ld {} \; If the command produces any output, this is a finding. Fix_Text At the command prompt, run the following command: # chown root:root <file_name> Repeat the command for each file that was returned. Note: Replace <file_name> for the name of the file that was returned. Not_Reviewed Vuln_Num V-256690 Rule_ID SV-256690r888626_rule Severity medium Rule_Title ESX Agent Manager must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail. Vuln_Discuss Determining a safe state for failure and weighing that against a potential denial of service for users depends on what type of application the web server is hosting. For the ESX Agent Manager, it is preferable that the service abort startup on any initialization failure rather than continuing in a degraded, and potentially insecure, state. Check_Content At the command line, run the following command: # grep EXIT_ON_INIT_FAILURE /etc/vmware-eam/catalina.properties Expected result: org.apache.catalina.startup.EXIT_ON_INIT_FAILURE=true If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /etc/vmware-eam/catalina.properties Add or change the following line: org.apache.catalina.startup.EXIT_ON_INIT_FAILURE=true Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256691 Rule_ID SV-256691r888629_rule Severity medium Rule_Title ESX Agent Manager must limit the number of allowed connections. Vuln_Discuss Limiting the number of established connections to the ESX Agent Manager is a basic denial-of-service protection. Servers where the limit is too high or unlimited could run out of system resources and negatively affect system availability. Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Connector/@acceptCount' /usr/lib/vmware-eam/web/conf/server.xml Expected result: acceptCount="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 Configure the <Connector> node with the value: acceptCount="300" Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256692 Rule_ID SV-256692r888632_rule Severity medium Rule_Title ESX Agent Manager must set URIEncoding to UTF-8. Vuln_Discuss Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode characters into hosted applications in an effort to break out of the document home or root home directory or bypass security checks. ESX Agent Manager must be configured to use a consistent character set via the "URIEncoding" attribute on the Connector nodes. Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Connector/@URIEncoding' /usr/lib/vmware-eam/web/conf/server.xml Expected result: URIEncoding="UTF-8" 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 Configure the <Connector> node with the value: URIEncoding="UTF-8" Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256693 Rule_ID SV-256693r888635_rule Severity medium Rule_Title ESX Agent Manager must use the "setCharacterEncodingFilter" filter. Vuln_Discuss Invalid user input occurs when a user inserts data or characters into a hosted application's data entry field and the hosted application is unprepared to process that data. This results in unanticipated application behavior, potentially leading to an application compromise. Invalid user input is one of the primary methods employed when attempting to compromise an application. An attacker can also enter Unicode characters into hosted applications in an effort to break out of the document home or root home directory or to bypass security checks. VMware uses the standard Tomcat "SetCharacterEncodingFilter" to provide a layer of defense against character encoding attacks. Filters are Java objects that perform filtering tasks on the request to a resource (a servlet or static content), on the response from a resource, or both. Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/filter-mapping/filter-name[text()="setCharacterEncodingFilter"]/parent::filter-mapping' - Expected result: <filter-mapping> <filter-name>setCharacterEncodingFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> If the output is does not match the expected result, this is a finding. At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/filter/filter-name[text()="setCharacterEncodingFilter"]/parent::filter' - Expected result: <filter> <filter-name>setCharacterEncodingFilter</filter-name> <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param> <init-param> <param-name>ignore</param-name> <param-value>true</param-value> </init-param> <async-supported>true</async-supported> </filter> If the output is does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Configure the <web-app> node with the child nodes listed below: <filter-mapping> <filter-name>setCharacterEncodingFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <filter> <filter-name>setCharacterEncodingFilter</filter-name> <filter-class>org.apache.catalina.filters.SetCharacterEncodingFilter</filter-class> <init-param> <param-name>encoding</param-name> <param-value>UTF-8</param-value> </init-param> <init-param> <param-name>ignore</param-name> <param-value>true</param-value> </init-param> <async-supported>true</async-supported> </filter> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256694 Rule_ID SV-256694r888638_rule Severity medium Rule_Title ESX Agent Manager must set the welcome-file node to a default web page. Vuln_Discuss Enumeration techniques, such as URL parameter manipulation, rely on being able to obtain information about the web server's directory structure by locating directories without default pages. In this scenario, the web server will display to the user a listing of the files in the directory being accessed. By having a default hosted application web page, the anonymous web user will not obtain directory browsing information or an error message that reveals the server type and version. Ensuring every document directory has an "index.jsp" (or equivalent) file is one approach to mitigating the vulnerability. Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/welcome-file-list' - Expected result: <welcome-file-list> <welcome-file>index.jsp</welcome-file> </welcome-file-list> If the output does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Add the following section under the <web-apps> node: <welcome-file-list> <welcome-file>index.jsp</welcome-file> </welcome-file-list> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256695 Rule_ID SV-256695r888641_rule Severity medium Rule_Title ESX Agent Manager must not show directory listings. Vuln_Discuss Enumeration techniques, such as URL parameter manipulation, rely on being able to obtain information about the web server's directory structure by locating directories without default pages. In this scenario, the web server will display to the user a listing of the files in the directory being accessed. Ensuring that directory listing is disabled is one approach to mitigating the vulnerability. In Tomcat, directory listing is disabled by default but can be enabled via the "listings" parameter. Ensure this node is not present to have the default effect. Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '//param-name[text()="listings"]/parent::init-param' - Expected result: XPath set is empty If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Find and remove the entire block returned in the check. Example: <init-param> <param-name>listings</param-name> <param-value>true</param-value> </init-param> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256696 Rule_ID SV-256696r888644_rule Severity medium Rule_Title ESX Agent Manager must be configured to show error pages with minimal information. Vuln_Discuss Web servers will often display error messages to client users, including enough information to aid in the debugging of the error. The information given back in error messages may display the web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage. This information could be used by an attacker to blueprint what type of attacks might be successful. Therefore, the ESX Agent Manager Service must be configured with a catchall error handler that redirects to a standard "error.jsp". Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/error-page/exception-type["text()=java.lang.Throwable"]/parent::error-page' - Expected result: <error-page> <exception-type>java.lang.Throwable</exception-type> <location>/error.jsp</location> </error-page> If the output does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Add the following section under the <web-apps> node: <error-page> <exception-type>java.lang.Throwable</exception-type> <location>/error.jsp</location> </error-page> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256697 Rule_ID SV-256697r888647_rule Severity medium Rule_Title ESX Agent Manager must be configured to not show error reports. Vuln_Discuss Web servers will often display error messages to client users, including enough information to aid in the debugging of the error. The information given back in error messages may display the web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage. This information could be used by an attacker to blueprint what type of attacks might be successful. Therefore, the Security Token Service must be configured with a catchall error handler that redirects to a standard "error.jsp". Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Engine/Host/Valve[@className="org.apache.catalina.valves.ErrorReportValve"]' /usr/lib/vmware-eam/web/conf/server.xml Expected result: <Valve className="org.apache.catalina.valves.ErrorReportValve" showServerInfo="false" showReport="false"/> If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/conf/server.xml Locate the following Host block: <Host ...> ... </Host> Inside this block, add the following on a new line: <Valve className="org.apache.catalina.valves.ErrorReportValve" showServerInfo="false" showReport="false"/> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256698 Rule_ID SV-256698r918905_rule Severity medium Rule_Title ESX Agent Manager must hide the server version. Vuln_Discuss Web servers will often display error messages to client users, including enough information to aid in the debugging of the error. The information given back in error messages may display the web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage. This information could be used by an attacker to blueprint what type of attacks might be successful. Therefore, the ESX Agent Manager service must be configured with a catch-all error handler that redirects to a standard "error.jsp". Check_Content At the command prompt, run the following command: # xmllint --xpath '/Server/Service/Connector/@server' /usr/lib/vmware-eam/web/conf/server.xml Expected result: server="Anonymous" If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/conf/server.xml Configure the <Connector> node with the value: server="Anonymous" Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256699 Rule_ID SV-256699r888653_rule Severity medium Rule_Title ESX Agent Manager must not enable support for TRACE requests. Vuln_Discuss "TRACE" is a technique for a user to request internal information about Tomcat. This is useful during product development but should not be enabled in production. Allowing an attacker to conduct a TRACE operation against ESX Agent Manager will expose information that would be useful to perform a more targeted attack. ESX Agent Manager provides the "allowTrace" parameter as means to disable responding to TRACE requests. Check_Content At the command prompt, run the following command: # grep allowTrace /usr/lib/vmware-eam/web/conf/server.xml If "allowTrace" is set to "true", this is a finding. If no line is returned, this is not a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/conf/server.xml Locate and navigate to 'allowTrace="true"'. Remove the 'allowTrace="true"' setting. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256700 Rule_ID SV-256700r918907_rule Severity medium Rule_Title ESX Agent Manager must have the debug option disabled. Vuln_Discuss Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server and plug-ins or modules being used. When debugging or trace information is enabled in a production web server, information about the web server, such as web server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application, and any backends being used for data storage may be displayed. Because this information may be placed in logs and general messages during normal operation of the web server, an attacker does not need to cause an error condition to gain this information. ESX Agent Manager can be configured to set the debugging level. By setting the debugging level to zero (0), no debugging information will be provided to a malicious user. Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '//param-name[text()="debug"]/parent::init-param' - Expected result: <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param> If the output does not match the expected result, this is a finding. If no lines are returned, this is not a finding. If "XPath set is empty" is returned, this is not a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Navigate to all <debug> nodes that are not set to "0". Set the <param-value> to "0" in all <param-name>debug</param-name> nodes. Note: The debug setting should look like the following: <init-param> <param-name>debug</param-name> <param-value>0</param-value> </init-param> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256701 Rule_ID SV-256701r888659_rule Severity medium Rule_Title Rsyslog must be configured to monitor and ship ESX Agent Manager log files. Vuln_Discuss ESX Agent Manager has a number of logs that must be offloaded from the originating system. This information can then be used for diagnostic, forensics, or other purposes relevant to ensuring the availability and integrity of the hosted application. Satisfies: SRG-APP-000358-WSR-000163, SRG-APP-000125-WSR-000071 Check_Content At the command prompt, run the following command: # rpm -V VMware-visl-integration|grep vmware-services-eam.conf|grep "^..5......" If the command returns any output, this is a finding. Fix_Text Navigate to and open: /etc/vmware-syslog/vmware-services-eam.conf Create the file if it does not exist. Set the contents of the file as follows: #eam.log input(type="imfile" File="/var/log/vmware/eam/eam.log" Tag="eam-main" Severity="info" Facility="local0") #eam web access logs input(type="imfile" File="/var/log/vmware/eam/web/localhost_access.log" Tag="eam-access" Severity="info" Facility="local0") #eam jvm logs input(type="imfile" File="/var/log/vmware/eam/jvm.log.stdout" Tag="eam-stdout" Severity="info" Facility="local0") input(type="imfile" File="/var/log/vmware/eam/jvm.log.stderr" Tag="eam-stderr" Severity="info" Facility="local0") #eam catalina logs input(type="imfile" File="/var/log/vmware/eam/web/catalina.log" Tag="eam-catalina" Severity="info" Facility="local0") #eam catalina localhost logs input(type="imfile" File="/var/log/vmware/eam/web/localhost.log" Tag="eam-catalina" Severity="info" Facility="local0") #eam firstboot logs input(type="imfile" File="/var/log/vmware/firstboot/eam_firstboot.py*.log" Tag="eam-firstboot" Severity="info" Facility="local0") Not_Reviewed Vuln_Num V-256702 Rule_ID SV-256702r888662_rule Severity medium Rule_Title ESX Agent Manager must set the secure flag for cookies. Vuln_Discuss The secure flag is an option that can be set by the application server when sending a new cookie to the user within an HTTP Response. The purpose of the secure flag is to prevent cookies from being observed by unauthorized parties due to the transmission of a cookie in clear text. By setting the secure flag, the browser will prevent the transmission of a cookie over an unencrypted channel. The ESX Agent Manager is configured to only be accessible over a Transport Layer Security (TLS) tunnel, but this cookie flag is still a recommended best practice. Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed 's/xmlns=".*"//g' | xmllint --xpath '/web-app/session-config/cookie-config/secure' - Expected result: <secure>true</secure> If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Navigate to the /<web-apps>/<session-config>/<cookie-config> node and configure it as follows: <cookie-config> <http-only>true</http-only> <secure>true</secure> </cookie-config> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256703 Rule_ID SV-256703r888665_rule Severity medium Rule_Title ESX Agent Manager must be configured with the appropriate ports. Vuln_Discuss Web servers provide numerous processes, features, and functionalities that use TCP/IP ports. Some of these processes may be deemed unnecessary or too unsecure to run on a production system. The ports the ESX Agent Manager listens on are configured in the "catalina.properties" file and must be verified as accurate to their shipping state. Check_Content At the command prompt, run the following command: # grep 'bio.http.port' /etc/vmware-eam/catalina.properties Expected result: bio.http.port=15005 If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /etc/vmware-eam/catalina.properties Navigate to the port's specification section. Set the ESX Agent Manager port specifications according to the following: bio.http.port=15005 Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256704 Rule_ID SV-256704r888668_rule Severity medium Rule_Title ESX Agent Manager must disable the shutdown port. Vuln_Discuss An attacker has at least two reasons to stop a web server. The first is to cause a denial of service, and the second is to put in place changes the attacker made to the web server configuration. If the Tomcat shutdown port feature is enabled, a shutdown signal can be sent to the ESX Agent Manager through this port. To ensure availability, the shutdown port must be disabled. Check_Content At the command prompt, run the following command: # grep 'base.shutdown.port' /etc/vmware-eam/catalina.properties Expected result: base.shutdown.port=-1 If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /etc/vmware-eam/catalina.properties Add or modify the setting "base.shutdown.port=-1" in the "catalina.properties" file. Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed Vuln_Num V-256705 Rule_ID SV-256705r888671_rule Severity medium Rule_Title ESX Agent Manager default servlet must be set to "readonly". Vuln_Discuss The default servlet (or DefaultServlet) is a special servlet provided with Tomcat that is called when no other suitable page is found in a particular folder. The DefaultServlet serves static resources as well as directory listings. The DefaultServlet is configured by default with the "readonly" parameter set to "true" where HTTP commands such as PUT and DELETE are rejected. Changing this to "false" allows clients to delete or modify static resources on the server and to upload new resources. DefaultServlet "readonly" must be set to "true", either literally or by absence (default). Check_Content At the command prompt, run the following command: # xmllint --format /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml | sed '2 s/xmlns=".*"//g' | xmllint --xpath '/web-app/servlet/servlet-name[text()="default"]/../init-param/param-name[text()="readonly"]/../param-value[text()="false"]' - Expected result: XPath set is empty If the output of the command does not match the expected result, this is a finding. Fix_Text Navigate to and open: /usr/lib/vmware-eam/web/webapps/eam/WEB-INF/web.xml Navigate to the /<web-apps>/<servlet>/<servlet-name>default</servlet-name>/ node and remove the following node: <init-param> <param-name>readonly</param-name> <param-value>false</param-value> </init-param> Restart the service with the following command: # vmon-cli --restart eam Not_Reviewed