| Finding ID |
Severity |
Title |
Description |
|
V-259036
|
Medium |
The vCenter ESX Agent Manager service host-manager webapp must be removed. |
Tomcat provides host management functionality through either a default host-manager webapp or through local editing of the configuration files. The host-manager webapp files must be deleted, and administration must be performed through the local editing of the configuration files. |
|
V-259035
|
Medium |
The vCenter ESX Agent Manager service manager webapp must be removed. |
Tomcat provides management functionality through either a default manager webapp or through local editing of the configuration files. The manager webapp files must be deleted, and administration must be performed through the local editing of the configuration files. |
|
V-259034
|
Medium |
The vCenter ESX Agent Manager service must enable "ENFORCE_ENCODING_IN_GET_WRITER". |
Some clients try to guess the character encoding of text media when the mandated default of ISO-8859-1 should be used. Some browsers will interpret as UTF-7 when the characters are safe for ISO-8859-1. This can create the potential for a XSS attack. To defend against this, enforce_encoding_in_get_writer must be set... |
|
V-259033
|
Medium |
The vCenter ESX Agent Manager service must disable "ALLOW_BACKSLASH". |
When Tomcat is installed behind a proxy configured to only allow access to certain contexts (web applications), an HTTP request containing "/\../" may allow attackers to work around the proxy restrictions using directory traversal attack methods. If "allow_backslash" is "true", the "\" character will be permitted as a path delimiter.... |
|
V-259032
|
Medium |
The vCenter ESX Agent Manager service files must have permissions in an out-of-the-box state. |
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. |
|
V-259031
|
Medium |
The vCenter ESX Agent Manager service default documentation must be removed. |
Tomcat provides documentation and other directories in the default installation that do not serve a production use. These files must be deleted. |
|
V-259030
|
Medium |
The vCenter ESX Agent Manager service default ROOT web application must be removed. |
The default ROOT web application includes the version of Tomcat being used, links to Tomcat documentation, examples, FAQs, and mailing lists. The default ROOT web application must be removed from a publicly accessible instance and a more appropriate default page shown to users. |
|
V-259029
|
Medium |
The vCenter ESX Agent Manager service example applications must be removed. |
Tomcat provides example applications, documentation, and other directories in the default installation that do not serve a production use. These files must be deleted. |
|
V-259028
|
Medium |
The vCenter ESX Agent Manager service xpoweredBy attribute must be disabled. |
Individual connectors can be configured to display the Tomcat information to clients. This information can be used to identify server versions that can be useful to attackers for identifying vulnerable versions of Tomcat. Individual connectors must be checked for the xpoweredBy attribute to ensure they do not pass server information... |
|
V-259027
|
Medium |
The vCenter ESX Agent Manager service must have Autodeploy disabled. |
Tomcat allows auto-deployment of applications while it is running. This can allow untested or malicious applications to be automatically loaded into production. Autodeploy must be disabled in production. |
|
V-259026
|
Medium |
The vCenter ESX Agent Manager service deployXML attribute must be disabled. |
The Host element controls deployment. Automatic deployment allows for simpler management but also makes it easier for an attacker to deploy a malicious application. Automatic deployment is controlled by the autoDeploy and deployOnStartup attributes. If both are false, only Contexts defined in server.xml will be deployed, and any changes will... |
|
V-259025
|
Medium |
The vCenter ESX Agent Manager service directory listings parameter must be disabled. |
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... |
|
V-259024
|
Medium |
The vCenter ESX Agent Manager service debug parameter must be disabled. |
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,... |
|
V-259023
|
Medium |
The vCenter ESX Agent Manager service shutdown port must be disabled. |
Tomcat by default listens on TCP port 8005 to accept shutdown requests. By connecting to this port and sending the SHUTDOWN command, all applications within Tomcat are halted. The shutdown port is not exposed to the network as it is bound to the loopback interface. Setting the port to "-1"... |
|
V-259022
|
Medium |
The vCenter ESX Agent Manager service DefaultServlet must be set to "readonly" for "PUT" and "DELETE" commands. |
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... |
|
V-259021
|
Medium |
The vCenter ESX Agent Manager service cookies must have the "http-only" flag set. |
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... |
|
V-259020
|
Medium |
The vCenter ESX Agent Manager service must configure the "setCharacterEncodingFilter" filter. |
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... |
|
V-259019
|
Medium |
The vCenter ESX Agent Manager service must limit the number of times that each Transmission Control Protocol (TCP) connection is kept alive. |
KeepAlive provides long lived HTTP sessions that allow multiple requests to be sent over the same connection. Enabling KeepAlive mitigates the effects of several types of denial-of-service attacks.
An advantage of KeepAlive is the reduced latency in subsequent requests (no handshaking). However, a disadvantage is that server resources are not... |
|
V-259018
|
Medium |
The vCenter ESX Agent Manager service must limit the amount of time that each Transmission Control Protocol (TCP) connection is kept alive. |
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... |
|
V-259017
|
Medium |
The vCenter ESX Agent Manager service must enable STRICT_SERVLET_COMPLIANCE. |
Strict Servlet Compliance forces Tomcat to adhere to standards specifications including but not limited to RFC2109. RFC2109 sets the standard for HTTP session management. This setting affects several other settings that primarily pertain to cookie headers, cookie values, and sessions. Cookies will be parsed for strict adherence to specifications.
Note... |
|
V-259016
|
Medium |
The vCenter ESX Agent Manager service must offload log records onto a different system or media from the system being logged. |
Information system logging capability is critical for accurate forensic analysis. Log record content that may be necessary to satisfy the requirement of this control includes, but is not limited to, time stamps, source and destination IP addresses, user/process identifiers, event descriptions, application-specific events, success/fail indications, filenames involved, and access control... |
|
V-259015
|
Medium |
The vCenter ESX Agent Manager service must set an inactive timeout for sessions. |
Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after a set period of inactivity, the web server can make certain that those sessions that are not closed... |
|
V-259014
|
Medium |
The vCenter ESX Agent Manager service "ErrorReportValve showServerInfo" must be set to "false". |
The Error Report Valve is a simple error handler for HTTP status codes that will generate and return HTML error pages. It can also be configured to return predefined static HTML pages for specific status codes and/or exception types. Disabling "showServerInfo" will only return the HTTP status code and remove... |
|
V-259013
|
Medium |
The vCenter ESX Agent Manager service must set URIEncoding to UTF-8. |
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... |
|
V-259012
|
Medium |
The vCenter ESX Agent Manager service must be configured to fail to a known safe state if system initialization fails. |
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. It is preferable that the service abort startup on any initialization failure rather than continuing in a degraded, and potentially insecure, state. |
|
V-259011
|
Medium |
The vCenter ESX Agent Manager service must be configured to limit data exposure between applications. |
If RECYCLE_FACADES is true or if a security manager is in use, a new facade object will be created for each request. This reduces the chances that a bug in an application might expose data from one request to another. |
|
V-259010
|
Medium |
The vCenter ESX Agent Manager service must be configured to use a specified IP address and port. |
The server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for server to use, the server will listen on all IP addresses available.
Accessing the hosted application through an IP address normally used for nonapplication functions opens the possibility... |
|
V-259009
|
Medium |
The vCenter ESX Agent Manager service must disable stack tracing. |
Stack tracing provides debugging information from the application call stacks when a runtime error is encountered. If stack tracing is left enabled, Tomcat will provide this call stack information to the requestor, which could result in the loss of sensitive information or data that could be used to compromise the... |
|
V-259008
|
Medium |
The vCenter ESX Agent Manager service must limit privileges for creating or modifying hosted application shared files. |
Application servers have the ability to specify that the hosted applications use shared libraries. The application server must have a capability to divide roles based upon duties wherein one project user (such as a developer) cannot modify the shared library code of another project user. The application server must also... |
|
V-259007
|
Medium |
The vCenter ESX Agent Manager service logs folder permissions must be set correctly. |
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... |
|
V-259006
|
Medium |
The vCenter ESX Agent Manager service must produce log records containing sufficient information regarding event details. |
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... |
|
V-259005
|
Medium |
The vCenter ESX Agent Manager service must initiate session logging upon startup. |
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... |
|
V-259004
|
Medium |
The vCenter ESX Agent Manager service cookies must have secure flag set. |
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... |
|
V-259003
|
Medium |
The vCenter ESX Agent Manager 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... |
