V-239747 | High | vSphere Client must be configured with FIPS 140-2 compliant ciphers for HTTPS connections. | Encryption of data in flight is an essential element of protecting information confidentiality. If a web server uses weak or outdated encryption algorithms, the server's communications can... |
V-239748 | High | vSphere Client must be configured to enable SSL/TLS. | Data exchanged between the user and the web server can range from static display data to credentials used to log into the hosted application. Even when data appears to be static, the non-displayed... |
V-239749 | High | vSphere Client must be configured to only communicate over TLS 1.2. | Data exchanged between the user and the web server can range from static display data to credentials used to log in to the hosted application. Even when data appears to be static, the... |
V-239767 | Medium | vSphere Client 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... |
V-239743 | Medium | vSphere Client must limit the amount of time that each 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... |
V-239746 | Medium | vSphere Client must protect cookies from 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... |
V-239744 | Medium | vSphere Client 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... |
V-239745 | Medium | vSphere Client 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.... |
V-239764 | Medium | vSphere Client 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... |
V-239765 | Medium | vSphere Client must be configured to show error pages with minimal information. | Web servers will often display error messages to client users, displaying enough information to aid in the debugging of the error. The information given back in error messages may display the web... |
V-239760 | Medium | vSphere Client directory tree 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.... |
V-239761 | Medium | vSphere Client must limit the number of allowed connections. | Limiting the number of established connections to Sphere Client is a basic denial-of-service protection. Servers where the limit is too high or unlimited can potentially run out of system... |
V-239762 | Medium | vSphere Client 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... |
V-239763 | Medium | vSphere Client 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... |
V-239768 | Medium | Rsyslog must be configured to monitor and ship vSphere Client log files. | The vSphere Client produces a handful of logs that must be offloaded from the originating system. This information can then be used for diagnostic, forensics, or other purposes relevant to... |
V-239769 | Medium | vSphere Client 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.... |
V-239755 | Medium | vSphere Client 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... |
V-239754 | Medium | vSphere Client must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled. | MIME mappings tell vSphere Client 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... |
V-239757 | Medium | vSphere Client 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, vSphere Client can continue to consume system resources, which will... |
V-239756 | Medium | vSphere Client 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... |
V-239751 | Medium | vSphere Client 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... |
V-239750 | Medium | vSphere Client must be configured to use the HTTPS scheme. | Data exchanged between the user and the web server can range from static display data to credentials used to log into the hosted application. Even when data appears to be static, the non-displayed... |
V-239753 | Medium | vSphere Client application files must be verified for their integrity. | Verifying that vSphere Client application code is unchanged from its shipping state is essential for file validation and non-repudiation of vSphere Client. There is no reason that the MD5 hash of... |
V-239752 | Medium | vSphere Client must generate log records during Java 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... |
V-239759 | Medium | vSphere Client must ensure appropriate permissions are set on the keystore. | The web server's private key is used to prove the identity of the server to clients and securely exchange the shared secret key used to encrypt communications between the web server and clients.... |
V-239758 | Medium | vSphere Client 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... |
V-239771 | Medium | vSphere Client 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... |
V-239770 | Medium | vSphere Client 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.... |
V-239766 | Medium | vSphere Client 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... |