| Finding ID |
Severity |
Title |
Description |
|
V-256644
|
Medium |
Performance Charts default servlet must be set to "readonly". |
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-256643
|
Medium |
Performance Charts must set the secure flag for cookies. |
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-256642
|
Medium |
Performance Charts must disable the shutdown port. |
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... |
|
V-256641
|
Medium |
Performance Charts must be configured with the appropriate ports. |
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 Performance Charts listens on are configured in the "catalina.properties" file and must be verified as accurate to their... |
|
V-256640
|
Medium |
Rsyslog must be configured to monitor and ship Performance Charts log files. |
Performance Charts produces several logs that must be offloaded from the originating system. This information can then be used for diagnostic purposes, forensics purposes, 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 |
|
V-256639
|
Medium |
Performance Charts must properly configure log sizes and rotation. |
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. Performance Charts properly sizes and configures log rotation during installation. This default configuration must be verified. |
|
V-256638
|
Medium |
Performance Charts must have the debug option turned off. |
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-256637
|
Medium |
Performance Charts must not enable support for TRACE requests. |
"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 Performance Charts will expose information that would be useful to perform a more targeted attack.... |
|
V-256636
|
Medium |
Performance Charts must hide the server version. |
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,... |
|
V-256635
|
Medium |
Performance Charts must be configured to not show error reports. |
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,... |
|
V-256634
|
Medium |
Performance Charts must be configured to show error pages with minimal information. |
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,... |
|
V-256633
|
Medium |
Performance Charts must not show directory listings. |
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 directory listing... |
|
V-256632
|
Medium |
Performance Charts must set the welcome-file node to a default web page. |
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... |
|
V-256631
|
Medium |
Performance Charts must use 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-256630
|
Medium |
Performance Charts 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-256629
|
Medium |
Performance Charts must limit the number of allowed connections. |
Limiting the number of established connections to Performance Charts 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. |
|
V-256628
|
Medium |
Performance Charts must fail to a known safe state if system initialization fails, shutdown fails, or aborts fail. |
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 Performance Charts, it is preferable that the service abort startup on any initialization failure rather than continuing in a degraded, and... |
|
V-256627
|
Medium |
Performance Charts directory tree must have permissions in an out-of-the-box state. |
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. Performance Charts files must be... |
|
V-256626
|
Medium |
Performance Charts must not have any symbolic links in the web content directory tree. |
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... |
|
V-256625
|
Medium |
Performance Charts must be configured with memory leak protection. |
The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, Performance Chart 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... |
|
V-256624
|
Medium |
Performance Charts must not have the Web Distributed Authoring (WebDAV) servlet installed. |
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... |
|
V-256623
|
Medium |
Performance Charts must have mappings set for Java servlet pages. |
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... |
|
V-256622
|
Medium |
Performance Charts must have Multipurpose Internet Mail Extensions (MIMEs) that invoke operating system shell programs disabled. |
MIME mappings tell Performance Charts 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... |
|
V-256621
|
Medium |
Performance Charts must be configured to limit access to internal packages. |
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.
Performance Charts... |
|
V-256620
|
Medium |
Performance Charts must not be configured with unsupported realms. |
Performance Charts performs user authentication at the application level and not through Tomcat. Depending on the vCenter Server Appliance (VCSA) version, Performance Charts may come configured with a "UserDatabaseRealm". This should be removed as part of eliminating unnecessary features. |
|
V-256619
|
Medium |
Performance Charts must only run one webapp. |
VMware ships Performance Charts on the vCenter Server Appliance (VCSA)with one webapp. Any other path is potentially malicious and must be removed. |
|
V-256618
|
Medium |
Performance Charts application files must be verified for their integrity. |
Verifying the Security Token Service application code is unchanged from its shipping state is essential for file validation and nonrepudiation of Performance Charts. There is no reason the MD5 hash of the RPM original files should be changed after installation, excluding configuration files. |
|
V-256617
|
Medium |
Performance Charts log files must only be modifiable by privileged users. |
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 undertake 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-256616
|
Medium |
Performance Charts must generate log records for system startup and shutdown. |
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... |
|
V-256615
|
Medium |
Performance Charts must record user access in a format that enables monitoring of remote access. |
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-256614
|
Medium |
Performance Charts must protect cookies from cross-site scripting (XSS). |
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.
When a cookie is tagged with the "HttpOnly" flag, it tells the... |
|
V-256613
|
Medium |
Performance Charts must limit the maximum size of a POST request. |
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. Performance Charts is configured... |
|
V-256612
|
Medium |
Performance Charts must limit the number of 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... |
|
V-256611
|
Medium |
Performance Charts must limit the amount of time that each Transport 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... |
