{"stig":{"title":"VMware vSphere 7.0 vCenter Appliance Lookup Service Security Technical Implementation Guide","version":"1","release":"2"},"checks":[{"vulnId":"V-256706","ruleId":"SV-256706r888709_rule","severity":"medium","ruleTitle":"Lookup Service must limit the amount of time that each Transport Control Protocol (TCP) connection is kept alive.","description":"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. \n\nIn 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.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Connector[@port=\"${bio-custom.http.port}\"]/@connectionTimeout' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nconnectionTimeout=\"60000\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nConfigure the <Connector> node with the value:\n\nconnectionTimeout=\"60000\"\n\nExample:\n\n<Connector .. connectionTimeout=\"60000\" ..>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000054"]},{"vulnId":"V-256707","ruleId":"SV-256707r888712_rule","severity":"medium","ruleTitle":"Lookup Service must limit the number of concurrent connections permitted.","description":"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.\n\nMitigating this kind of attack will include limiting the number of concurrent HTTP/HTTPS requests. 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.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Connector[@port=\"${bio-custom.http.port}\"]/@maxThreads' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nXPath set is empty\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nIn the <Connector> node, remove the \"maxThreads\" key/value pair.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000054"]},{"vulnId":"V-256708","ruleId":"SV-256708r888715_rule","severity":"medium","ruleTitle":"Lookup Service must limit the maximum size of a POST request.","description":"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.\n\nIf \"maxPostSize\" is not set, the default value of 2097152 (2MB) is used. Lookup Service is configured in its shipping state to not set a value for \"maxPostSize\".","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Connector[@port=\"${bio-custom.http.port}\"]/@maxPostSize' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nXPath set is empty\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nIn the <Connector> node, remove the \"maxPostSize\" key/value pair.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000054"]},{"vulnId":"V-256709","ruleId":"SV-256709r888718_rule","severity":"medium","ruleTitle":"Lookup Service must protect cookies from cross-site scripting (XSS).","description":"Cookies are a common way to save session state over the HTTP(S) protocol. If an attacker can compromise session data stored in a cookie, they are better able to launch an attack against the server and its applications.\n\nWhen a cookie is tagged with the \"HttpOnly\" flag, it tells the browser that this particular cookie should only be accessed by the originating server. Any attempt to access the cookie from client script is strictly forbidden.\n\nSatisfies: SRG-APP-000001-WSR-000002, SRG-APP-000223-WSR-000011, SRG-APP-000439-WSR-000154","checkContent":"At the command prompt, run the following command:\n\n# xmllint --format /usr/lib/vmware-lookupsvc/conf/context.xml | xmllint --xpath '/Context/@useHttpOnly' -\n\nExpected result:\n\nuseHttpOnly=\"true\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/context.xml\n\nAdd the following configuration to the <Context> node:\n\nuseHttpOnly=\"true\"\n\nExample:\n\n<Context useHttpOnly=\"true\">\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000054","CCI-001664","CCI-002418"]},{"vulnId":"V-256710","ruleId":"SV-256710r888721_rule","severity":"medium","ruleTitle":"Lookup Service must record user access in a format that enables monitoring of remote access.","description":"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.\n\nTomcat 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.\n\nSatisfies: SRG-APP-000016-WSR-000005, 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","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Engine/Host/Valve[@className=\"org.apache.catalina.valves.AccessLogValve\"]/@pattern' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\npattern=\"%t %I [RemoteIP] %{X-Forwarded-For}i %u [Request] %h:%{remote}p to local %{local}p - %H %m %U%q    [Response] %s - %b bytes    [Perf] process %Dms / commit %Fms / conn [%X]\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nInside the <Host> node, find the \"AccessLogValve\" <Valve> node and replace the \"pattern\" element as follows:\n\npattern=\"%t %I [RemoteIP] %{X-Forwarded-For}i %u [Request] %h:%{remote}p to local %{local}p - %H %m %U%q    [Response] %s - %b bytes    [Perf] process %Dms / commit %Fms / conn [%X]\"\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000067","CCI-000130","CCI-000131","CCI-000132","CCI-000133","CCI-000134","CCI-001462","CCI-001487","CCI-001889","CCI-001890"]},{"vulnId":"V-256711","ruleId":"SV-256711r888724_rule","severity":"medium","ruleTitle":"Lookup Service must generate log records for system startup and shutdown.","description":"Logging must be started as soon as possible when a service starts and 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.\n\nOn the vCenter Server Appliance (VCSA), the \"vmware-vmon\" service starts up the Java virtual machines (JVMs) for various vCenter processes, including Lookup Service, and the individual json configuration files control the early JVM logging. Ensuring these json files are configured correctly enables early Java \"stdout\" and \"stderr\" logging.\n\nSatisfies: SRG-APP-000089-WSR-000047, SRG-APP-000092-WSR-000055","checkContent":"At the command prompt, run the following command:\n\n# grep StreamRedirectFile /etc/vmware/vmware-vmon/svcCfgfiles/lookupsvc.json\n\nExpected result:\n\n\"StreamRedirectFile\": \"%VMWARE_LOG_DIR%/vmware/lookupsvc/lookupsvc_stream.log\",\n\nIf no log file is specified for the \"StreamRedirectFile\" setting, this is a finding.","fixText":"Navigate to and open:\n\n/etc/vmware/vmware-vmon/svcCfgfiles/lookupsvc.json\n\nBelow the last line of the \"PreStartCommandArg\" block, add or reconfigure the following line:\n\n\"StreamRedirectFile\": \"%VMWARE_LOG_DIR%/vmware/lookupsvc/lookupsvc_stream.log\",\n\nRestart the appliance for changes to take effect.","ccis":["CCI-000169","CCI-001464"]},{"vulnId":"V-256712","ruleId":"SV-256712r918958_rule","severity":"medium","ruleTitle":"Lookup Service log files must only be accessible by privileged users.","description":"Log data is essential in the investigation of events. If log data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult, if not impossible, to achieve.\n\nIn addition, access to log records provides information an attacker could use to their advantage because each event record might contain communication ports, protocols, services, trust relationships, usernames, etc. The Lookup Service restricts all access to log files by default, but this configuration must be verified.\n\nSatisfies: SRG-APP-000118-WSR-000068, SRG-APP-000119-WSR-000069, SRG-APP-000120-WSR-000070","checkContent":"At the command prompt, run the following command:\n\n# find /var/log/vmware/lookupsvc -xdev -type f ! -name lookupsvc-init.log -a '(' -perm -o+w -o -not -user lookupsvc -o -not -group lookupsvc ')' -exec ls -ld {} \\;\n\nIf any files are returned, this is a finding.\n\nNote: Prior to Update 3h, the user and group should be root.","fixText":"At the command prompt, run the following commands:\n\n# chmod o-w /var/log/vmware/lookupsvc/<file>\n# chown lookupsvc:lookupsvc /var/log/vmware/lookupsvc/<file>\n\nNote: Substitute <file> with the listed file.","ccis":["CCI-000162","CCI-000163","CCI-000164"]},{"vulnId":"V-256713","ruleId":"SV-256713r888730_rule","severity":"medium","ruleTitle":"Lookup Service application files must be verified for their integrity.","description":"Verifying the Lookup Service application code is unchanged from its shipping state is essential for file validation and nonrepudiation of the Lookup Service. There is no reason the MD5 hash of the RPM original files should be changed after installation, excluding configuration files.","checkContent":"At the command prompt, run the following command:\n\n# rpm -V vmware-lookupsvc|grep \"^..5......\"|grep -E \"\\.war|\\.jar|\\.sh|\\.py\"\n\nIf there is any output, this is a finding.","fixText":"Reinstall the vCenter Server Appliance (VCSA) or roll back to a backup. VMware does not support modifying the Lookup Service installation files manually.","ccis":["CCI-001749"]},{"vulnId":"V-256714","ruleId":"SV-256714r888733_rule","severity":"medium","ruleTitle":"Lookup Service must only run one webapp.","description":"VMware ships Lookup Service on the vCenter Server Appliance (VCSA) with one webapp. Any other path is potentially malicious and must be removed.","checkContent":"At the command prompt, run the following command:\n\n# ls -A /usr/lib/vmware-lookupsvc/webapps/*.war\n\nExpected result:\n\n/usr/lib/vmware-lookupsvc/webapps/ROOT.war\n\nIf the output does not match the expected result, this is a finding.","fixText":"For each unexpected directory returned in the check, run the following command:\n\n# rm /usr/lib/vmware-lookupsvc/webapps/<NAME>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001749"]},{"vulnId":"V-256715","ruleId":"SV-256715r888736_rule","severity":"medium","ruleTitle":"Lookup Service must not be configured with the \"UserDatabaseRealm\" enabled.","description":"The Lookup Service performs user authentication at the application level and not through Tomcat. By default, there is no configuration for the \"UserDatabaseRealm\" Tomcat authentication mechanism. As part of eliminating unnecessary features and to ensure the Lookup Service remains in its shipping state, the lack of a \"UserDatabaseRealm\" configuration must be confirmed.","checkContent":"At the command prompt, run the following command:\n\n# grep UserDatabaseRealm /usr/lib/vmware-lookupsvc/conf/server.xml\n\nIf the command produces any output, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nRemove all <Realm> nodes.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000381"]},{"vulnId":"V-256716","ruleId":"SV-256716r888739_rule","severity":"medium","ruleTitle":"Lookup Service must be configured to limit access to internal packages.","description":"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. \n\nThe Lookup Service comes preconfigured with the appropriate packages defined in \"package.access\", and this configuration must be maintained.","checkContent":"At the command prompt, run the following command:\n\n# grep \"package.access\" /usr/lib/vmware-lookupsvc/conf/catalina.properties\n\nExpected result:\n\npackage.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-sso/vmware-sts/conf/catalina.properties\n\nEnsure the \"package.access\" line is configured as follows:\n\npackage.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000381"]},{"vulnId":"V-256717","ruleId":"SV-256717r888742_rule","severity":"medium","ruleTitle":"Lookup Service must have Multipurpose Internet Mail Extensions (MIMEs) that invoke operating system shell programs disabled.","description":"MIME mappings tell the Lookup Service 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 that 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.","checkContent":"At the command prompt, run the following command:\n\n# grep -En '(x-csh<)|(x-sh<)|(x-shar<)|(x-ksh<)' /usr/lib/vmware-lookupsvc/conf/web.xml\n\nIf the command produces any output, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nRemove all of the following nodes lines:\n\n<mime-type>application/x-csh</mime-type>\n<mime-type>application/x-shar</mime-type>\n<mime-type>application/x-sh</mime-type>\n<mime-type>application/x-ksh</mime-type>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc\n\nNote: Delete the entire mime-mapping node for the target mime-type.\n\nExample:\n\n<mime-mapping>\n    <extension>sh</extension>\n    <mime-type>application/x-sh</mime-type>\n</mime-mapping>","ccis":["CCI-000381"]},{"vulnId":"V-256718","ruleId":"SV-256718r888745_rule","severity":"medium","ruleTitle":"Lookup Service must have mappings set for Java servlet pages.","description":"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.\n\nBy 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. \n\nBecause Tomcat is a Java-based web server, the main file extension used is *.jsp. This check ensures the *.jsp and *.jspx file types has been properly mapped to servlets.","checkContent":"At the command prompt, run the following command: \n\n# xmllint --format /usr/lib/vmware-lookupsvc/conf/web.xml | sed 's/xmlns=\".*\"//g' | xmllint --xpath '/web-app/servlet-mapping/servlet-name[text()=\"jsp\"]/parent::servlet-mapping' -\n\nExpected result:\n\n<servlet-mapping>\n    <servlet-name>jsp</servlet-name>\n    <url-pattern>*.jsp</url-pattern>\n    <url-pattern>*.jspx</url-pattern>\n</servlet-mapping>\n\nIf the .jsp and .jspx file url-patterns are not configured as in the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nNavigate to and locate the mapping for the JSP servlet. It is the <servlet-mapping> node that contains <servlet-name>jsp</servlet-name>.\n\nConfigure the <servlet-mapping> node to look like the code snippet below:\n\n<!-- The mappings for the JSP servlet -->\n<servlet-mapping>\n  <servlet-name>jsp</servlet-name>\n  <url-pattern>*.jsp</url-pattern>\n  <url-pattern>*.jspx</url-pattern>\n</servlet-mapping>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000381"]},{"vulnId":"V-256719","ruleId":"SV-256719r888748_rule","severity":"medium","ruleTitle":"Lookup Service must not have the Web Distributed Authoring (WebDAV) servlet installed.","description":"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.\n\nTomcat 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. Lookup Service does not configure WebDAV by default.","checkContent":"At the command prompt, run the following command: \n\n# grep -n 'webdav' /usr/lib/vmware-lookupsvc/conf/web.xml\n\nIf the command produces any output, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nFind the <servlet-name>webdav</servlet-name> node and remove the entire parent <servlet> block.\n\nFind the <servlet-name>webdav</servlet-name> node and remove the entire parent <servlet-mapping> block.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000381"]},{"vulnId":"V-256720","ruleId":"SV-256720r888751_rule","severity":"medium","ruleTitle":"Lookup Service must be configured with memory leak protection.","description":"The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, Lookup Service can continue to consume system resources, which will lead to \"OutOfMemoryErrors\" when reloading web applications.\n\nMemory 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 that the hosted application does not consume system resources and cause an unstable environment.","checkContent":"At the command prompt, run the following command: \n\n# grep JreMemoryLeakPreventionListener /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\n<Listener className=\"org.apache.catalina.core.JreMemoryLeakPreventionListener\"/>\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nNavigate to the <Server> node.\n\nAdd '<Listener className=\"org.apache.catalina.core.JreMemoryLeakPreventionListener\"/>' to the <Server> node.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-000381"]},{"vulnId":"V-256721","ruleId":"SV-256721r888754_rule","severity":"medium","ruleTitle":"Lookup Service must not have any symbolic links in the web content directory tree.","description":"A web server is designed to deliver content and execute scripts or applications on 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.\n\nBy 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.","checkContent":"At the command prompt, run the following command:\n\n# find /usr/lib/vmware-vsphere-ui/server/static/ -type l -ls\n\nIf the command produces any output, this is a finding.","fixText":"At the command prompt, run the following command:\n\nNote: Replace <file_name> for the name of any files that were returned.\n\n# unlink <file_name>\n\nRepeat the commands for each file that was returned.","ccis":["CCI-000381"]},{"vulnId":"V-256722","ruleId":"SV-256722r888757_rule","severity":"medium","ruleTitle":"Lookup Service directory tree must have permissions in an out-of-the-box state.","description":"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. Lookup Service files must be adequately protected with correct permissions as applied out of the box.\n\nSatisfies: SRG-APP-000211-WSR-000030, SRG-APP-000380-WSR-000072","checkContent":"At the command prompt, run the following command:\n\n# find  /usr/lib/vmware-lookupsvc/lib  /usr/lib/vmware-lookupsvc/conf -xdev -type f -a '(' -perm -o+w -o -not -user root -o -not -group root ')' -exec ls -ld {} \\;\n\nIf the command produces any output, this is a finding.","fixText":"At the command prompt, run the following commands:\n\n# chmod o-w <file>\n# chown root:root <file>\n\nRepeat the command for each file that was returned.","ccis":["CCI-001082","CCI-001813"]},{"vulnId":"V-256723","ruleId":"SV-256723r888760_rule","severity":"medium","ruleTitle":"Lookup Service must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail.","description":"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 Lookup Service, it is preferable that the service abort startup on any initialization failure rather than continuing in a degraded, and potentially insecure, state.","checkContent":"At the command line, run the following command:\n\n# grep EXIT_ON_INIT_FAILURE /usr/lib/vmware-lookupsvc/conf/catalina.properties\n\nExpected result:\n\norg.apache.catalina.startup.EXIT_ON_INIT_FAILURE=true\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/catalina.properties\n\nAdd or change the following line:\n\norg.apache.catalina.startup.EXIT_ON_INIT_FAILURE=true\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001190"]},{"vulnId":"V-256724","ruleId":"SV-256724r888763_rule","severity":"medium","ruleTitle":"Lookup Service must limit the number of allowed connections.","description":"Limiting the number of established connections is a basic denial-of-service protection and a best practice. Servers where the limit is too high or unlimited could run out of system resources and negatively affect system availability.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Connector[@port=\"${bio-custom.http.port}\"]/@acceptCount' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nacceptCount=\"100\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nNavigate to the <Connector> configured with port=\"${bio-custom.http.port}\".\n\nAdd or change the following value:\n\nacceptCount=\"100\"\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001094"]},{"vulnId":"V-256725","ruleId":"SV-256725r888766_rule","severity":"medium","ruleTitle":"Lookup Service must set URIEncoding to UTF-8.","description":"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. \n\nAn 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. Lookup Service must be configured to use a consistent character set via the \"URIEncoding\" attribute on the Connector nodes.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Connector[@port=\"${bio-custom.http.port}\"]/@URIEncoding' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nURIEncoding=\"UTF-8\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nNavigate to each of the <Connector> nodes.\n\nConfigure each <Connector> node with the value 'URIEncoding=\"UTF-8\"'.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001310"]},{"vulnId":"V-256726","ruleId":"SV-256726r888769_rule","severity":"medium","ruleTitle":"Lookup Service must set the welcome-file node to a default web page.","description":"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.\n\nBy 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 that every document directory has an \"index.jsp\" (or equivalent) file is one approach to mitigating the vulnerability.","checkContent":"At the command prompt, run the following command:\n \n# xmllint --format /usr/lib/vmware-lookupsvc/conf/web.xml | sed 's/xmlns=\".*\"//g' | xmllint --xpath '/web-app/welcome-file-list' -\n\nExpected result:\n\n<welcome-file-list>\n    <welcome-file>index.html</welcome-file>\n    <welcome-file>index.htm</welcome-file>\n    <welcome-file>index.jsp</welcome-file>\n</welcome-file-list>\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nAdd the following section under the <web-apps> node:\n\n<welcome-file-list>\n  <welcome-file>index.html</welcome-file>\n  <welcome-file>index.htm</welcome-file>\n  <welcome-file>index.jsp</welcome-file>\n</welcome-file-list>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001312"]},{"vulnId":"V-256727","ruleId":"SV-256727r888772_rule","severity":"medium","ruleTitle":"The Lookup Service must not show directory listings.","description":"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.\n\nIn 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.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --format /usr/lib/vmware-lookupsvc/conf/web.xml | sed 's/xmlns=\".*\"//g' | xmllint --xpath '//param-name[text()=\"listings\"]/..' -\n\nExpected result:\n\n<init-param>\n      <param-name>listings</param-name>\n      <param-value>false</param-value>\n</init-param>\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nSet the <param-value> to \"false\" in all <param-name>listing</param-name> nodes.\n\nThe setting should look like the following:\n\n<init-param>\n      <param-name>listings</param-name>\n      <param-value>false</param-value>\n</init-param>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001312"]},{"vulnId":"V-256728","ruleId":"SV-256728r888775_rule","severity":"medium","ruleTitle":"Lookup Service must be configured to hide the server version.","description":"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.\n\nThis information could be used by an attacker to blueprint what type of attacks might be successful. Therefore, Lookup Service must be configured to hide the server version at all times.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Connector[@port=\"${bio-custom.http.port}\"]/@server' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nserver=\"Anonymous\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nNavigate to each of the <Connector> nodes.\n\nConfigure each <Connector> node with 'server=\"Anonymous\"'.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001312"]},{"vulnId":"V-256729","ruleId":"SV-256729r888778_rule","severity":"medium","ruleTitle":"Lookup Service must be configured to show error pages with minimal information.","description":"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.\n\nThis information could be used by an attacker to blueprint what type of attacks might be successful. Therefore, the Lookup Service must be configured with a catchall error handler that redirects to a standard \"error.jsp\".","checkContent":"At the command prompt, run the following command:\n\n# xmllint --xpath '/Server/Service/Engine/Host/Valve[@className=\"org.apache.catalina.valves.ErrorReportValve\"]' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\n<Valve className=\"org.apache.catalina.valves.ErrorReportValve\" showServerInfo=\"false\" showReport=\"false\"/>\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nLocate the following Host block:\n\n<Host ...>\n...\n</Host>\n\nInside this block, add the following on a new line:\n\n<Valve className=\"org.apache.catalina.valves.ErrorReportValve\" showServerInfo=\"false\" showReport=\"false\"/>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001312"]},{"vulnId":"V-256730","ruleId":"SV-256730r888781_rule","severity":"medium","ruleTitle":"Lookup Service must not enable support for TRACE requests.","description":"\"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 the service will expose information that would be useful to perform a more targeted attack. Lookup Service provides the \"allowTrace\" parameter as means to disable responding to TRACE requests.","checkContent":"At the command prompt, run the following command:\n\n# grep allowTrace /usr/lib/vmware-lookupsvc/conf/server.xml\n\nIf \"allowTrace\" is set to \"true\", this is a finding.\n\nIf no line is returned, this is not a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nLocate and navigate to 'allowTrace=\"true\"'.\n\nRemove the 'allowTrace=\"true\"' setting.\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001312"]},{"vulnId":"V-256731","ruleId":"SV-256731r888784_rule","severity":"medium","ruleTitle":"Lookup Service must have the debug option turned off.","description":"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.\n\nBecause 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.\n\nLookup Service 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.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --format /usr/lib/vmware-lookupsvc/conf/web.xml | sed 's/xmlns=\".*\"//g' | xmllint --xpath '//param-name[text()=\"debug\"]/..' -\n\nExpected result:\n\n<init-param>\n  <param-name>debug</param-name>\n  <param-value>0</param-value>\n</init-param>\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nNavigate to all <debug> nodes that are not set to \"0\".\n\nSet the <param-value> to \"0\" in all <param-name>debug</param-name> nodes.\n\nNote: The debug setting should look like the following:\n\n<init-param>\n  <param-name>debug</param-name>\n  <param-value>0</param-value>\n</init-param>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001312"]},{"vulnId":"V-256732","ruleId":"SV-256732r888787_rule","severity":"medium","ruleTitle":"Lookup Service must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the web server.","description":"To ensure the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism must be able to allocate log record storage capacity. Lookup Service configures log sizes and rotation appropriately as part of its installation routine.\n\nVerifying the logging configuration file (logging.properties) has not been modified is sufficient to determine if the logging configuration has been modified from the default.","checkContent":"At the command prompt, run the following command:\n\n# rpm -V vmware-lookupsvc|grep logging.properties|grep \"^..5......\"\n\nIf the above command returns any output, this is a finding.","fixText":"Reinstall the vCenter Server Appliance (VCSA) or roll back to a backup. VMware does not support modifying the Lookup Service installation files manually.","ccis":["CCI-001849"]},{"vulnId":"V-256733","ruleId":"SV-256733r888790_rule","severity":"medium","ruleTitle":"Lookup Service log files must be offloaded to a central log server in real time.","description":"Lookup Service produces several 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.\n\nSatisfies: SRG-APP-000358-WSR-000163, SRG-APP-000108-WSR-000166, SRG-APP-000125-WSR-000071","checkContent":"At the command prompt, run the following command:\n\n# rpm -V VMware-visl-integration|grep vmware-services-lookupsvc.conf\n\nIf the above command returns any output, this is a finding.","fixText":"Navigate to and open:\n\n/etc/vmware-syslog/vmware-services-lookupsvc.conf\n\nCreate the file if it does not exist.\n\nSet the contents of the file as follows:\n\n#localhost_access_log\ninput(type=\"imfile\"\n      File=\"/var/log/vmware/lookupsvc/tomcat/localhost_access.log\"\n      Tag=\"lookupsvc-localhost_access\"\n      Severity=\"info\"\n      Facility=\"local0\")\n#lookupsvc_stream.log.std\ninput(type=\"imfile\"\n      File=\"/var/log/vmware/lookupsvc/lookupsvc_stream.log.std*\"\n      Tag=\"lookupsvc-std\"\n      Severity=\"info\"\n      Facility=\"local0\")\n#lookupserver-default\ninput(type=\"imfile\"\n      File=\"/var/log/vmware/lookupsvc/lookupserver-default.log\"\n      Tag=\"lookupsvc-lookupserver-default\"\n      Severity=\"info\"\n      Facility=\"local0\")\n#lookupServer\ninput(type=\"imfile\"\n      File=\"/var/log/vmware/lookupsvc/lookupServer.log\"\n      Tag=\"lookupsvc-lookupServer\"\n      Severity=\"info\"\n      Facility=\"local0\")\n#ls-perflogs\ninput(type=\"imfile\"\n      File=\"/var/log/vmware/lookupsvc/vmware-lookupservice-perf.log\"\n      Tag=\"lookupsvc-perf\"\n      Severity=\"info\"\n      Facility=\"local0\")\n#ls-gc\ninput(type=\"imfile\"\n      File=\"/var/log/vmware/lookupsvc/vmware-lookupsvc-gc.log.*.current\"\n      Tag=\"lookupsvc-gc\"\n      Severity=\"info\"\n      Facility=\"local0\")","ccis":["CCI-000139","CCI-001348","CCI-001851"]},{"vulnId":"V-256734","ruleId":"SV-256734r888793_rule","severity":"medium","ruleTitle":"Lookup Service must be configured with the appropriate ports.","description":"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 that Lookup Service listens on are configured in the \"catalina.properties\" file and must be verified as accurate to their shipping state.","checkContent":"At the command prompt, run the following command:\n\n# grep '\\.port' /usr/lib/vmware-lookupsvc/conf/catalina.properties\n\nExpected result:\n\nbase.shutdown.port=-1\nbase.jmx.port=-1\nbio-custom.http.port=7090\nbio-custom.https.port=8443\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/catalina.properties\n\nNavigate to the port's specification section.\n\nSet the Lookup Service port specifications according to the shipping configuration below:\n\nbase.shutdown.port=-1\nbase.jmx.port=-1\nbio-custom.http.port=7090\nbio-custom.https.port=8443\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-001762"]},{"vulnId":"V-256735","ruleId":"SV-256735r888796_rule","severity":"medium","ruleTitle":"Lookup Service must disable the shutdown port.","description":"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 Lookup Service through this port. To ensure availability, the shutdown port must be disabled.","checkContent":"At the command prompt, run the following commands:\n\n# xmllint --xpath '/Server/@port' /usr/lib/vmware-lookupsvc/conf/server.xml\n\nExpected result:\n\nport=\"${base.shutdown.port}\"\n\nIf the output does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/server.xml\n\nEnsure the server port is set as follows:\n\n<Server port=\"${base.shutdown.port}\">\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-002385"]},{"vulnId":"V-256736","ruleId":"SV-256736r888799_rule","severity":"medium","ruleTitle":"Lookup Service must set the secure flag for cookies.","description":"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 the cookie in clear text.\n\nBy setting the secure flag, the browser will prevent the transmission of a cookie over an unencrypted channel. Lookup Service is configured to only be accessible over a Transport Layer Security (TLS) tunnel, but this cookie flag is still a recommended best practice.","checkContent":"At the command prompt, run the following command:\n\n# xmllint --format /usr/lib/vmware-lookupsvc/conf/web.xml | sed 's/xmlns=\".*\"//g' | xmllint --xpath '/web-app/session-config/cookie-config/secure' -\n\nExpected result:\n\n<secure>true</secure>\n\nIf the output of the command does not match the expected result, this is a finding.","fixText":"Navigate to and open:\n\n/usr/lib/vmware-lookupsvc/conf/web.xml\n\nNavigate to the /<web-apps>/<session-config>/<cookie-config> node and configure it as follows:\n\n    <cookie-config>\n      <http-only>true</http-only>\n      <secure>true</secure>\n    </cookie-config>\n\nRestart the service with the following command:\n\n# vmon-cli --restart lookupsvc","ccis":["CCI-002418"]}]}