| Finding ID |
Severity |
Title |
Description |
|
V-256672
|
High |
VAMI must enable FIPS mode. |
Encryption is only as good as the encryption modules used. Unapproved cryptographic module algorithms cannot be verified and cannot be relied on to provide confidentiality or integrity, and DOD data may be compromised due to weak algorithms. FIPS 140-2 is the current standard for validating cryptographic modules. |
|
V-256646
|
High |
VAMI 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 could be compromised.
The U.S. Federal Information Processing Standards (FIPS) publication 140-2, Security Requirements for Cryptographic Modules (FIPS 140-2), identifies 11 areas for a... |
|
V-256671
|
Medium |
VAMI must be configured to hide the server type and version in client responses. |
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 server type, version, patches installed, plug-ins and modules installed, type of code being used by the hosted application,... |
|
V-256670
|
Medium |
VAMI must disable client-initiated Transport Layer Security (TLS) renegotiation. |
All versions of the Secure Sockets Layer (SSL) and TLS protocols (up to and including TLS 1.2) are vulnerable to a man-in-the-middle attack (CVE-2009-3555) during a renegotiation. This vulnerability allows an attacker to "prefix" a chosen plaintext to the HTTP request as seen by the web server. The protocols have... |
|
V-256669
|
Medium |
VAMI must force clients to select the most secure cipher. |
During a Transport Layer Security (TLS) session negotiation, when choosing a cipher during a handshake, normally the client's preference is used. This is potentially problematic as a malicious, dated, or poorly configured client could select the most insecure cipher offered by the server, even if it supports stronger ones.
If... |
|
V-256668
|
Medium |
VAMI must implement Transport Layer Security (TLS) 1.2 exclusively. |
TLS is a required transmission protocol for a web server hosting controlled information. The use of TLS provides confidentiality of data in transit between the web server and client. FIPS 140-2 approved TLS versions must be enabled, and non-FIPS-approved Secure Sockets Layer (SSL) versions must be disabled.
VAMI comes configured... |
|
V-256667
|
Medium |
VAMI must be protected from being stopped by a nonprivileged user. |
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. Therefore, only administrators should ever be able to stop VAMI.
The VAMI... |
|
V-256666
|
Medium |
VAMI must have debug logging 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-256665
|
Medium |
VAMI must not be configured to use "mod_status". |
Any application providing too much information in error logs and in administrative messages to the screen risks compromising the data and security of the application and system.
VAMI must only generate error messages that provide information necessary for corrective actions without revealing sensitive or potentially harmful information in error logs... |
|
V-256664
|
Medium |
VAMI must disable directory browsing. |
The goal is to completely control the web user's experience in navigating any portion of the web document root directories. Ensuring all web content directories have at least the equivalent of an "index.html" file is a significant factor to accomplish this end.
Enumeration techniques, such as Uniform Resource Locator (URL)... |
|
V-256663
|
Medium |
VAMI must set the encoding for all text Multipurpose Internet Mail Extensions (MIME) types 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-256662
|
Medium |
VAMI must protect against or limit the effects of HTTP types of denial-of-service (DoS) attacks. |
In UNIX and related computer operating systems, a file descriptor is an indicator used to access a file or other input/output resource, such as a pipe or network connection. File descriptors index into a per-process file descriptor table maintained by the kernel, which in turn indexes into a systemwide table... |
|
V-256661
|
Medium |
VAMI must protect the keystore from unauthorized access. |
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. By gaining access to the private key, an attacker can pretend to be an authorized server and... |
|
V-256660
|
Medium |
VAMI must prevent hosted applications from exhausting system resources. |
Most of the attention to denial-of-service (DoS) attacks focuses on ensuring that systems and applications are not victims of these attacks. However, these systems and applications must also be secured against use to launch such an attack against others.
A variety of technologies exist to limit or, in some cases,... |
|
V-256659
|
Medium |
VAMI must not have the Web Distributed Authoring (WebDAV) servlet installed. |
A web server can be installed with functionality that, by its nature, is not secure. 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. Allowing this functionality,... |
|
V-256658
|
Medium |
VAMI must have resource mappings set to disable the serving of certain file types. |
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 to identify which file types are not to be delivered to a client.
By not specifying which files can and... |
|
V-256657
|
Medium |
VAMI must remove all mappings to unused scripts. |
Scripts allow server-side processing on behalf of the hosted application user or as processes needed in the implementation of hosted applications. Removing scripts not needed for application operation or deemed vulnerable helps to secure the web server. To ensure scripts are not added to the web server and run maliciously,... |
|
V-256656
|
Medium |
VAMI must explicitly disable Multipurpose Internet Mail Extensions (MIME) mime mappings based on "Content-Type". |
Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view... |
|
V-256655
|
Medium |
VAMI must have Multipurpose Internet Mail Extensions (MIME) that invoke operating system shell programs disabled. |
Controlling what a user of a hosted application can access is part of the security posture of the web server. Any time a user can access more functionality than is needed for the operation of the hosted application poses a security issue. A user with too much access can view... |
|
V-256654
|
Medium |
VAMI must only load allowed server modules. |
A web server can provide many features, services, and processes. Some of these may be deemed unnecessary or too unsecure to run on a production DOD system.
VAMI can be configured to load any number of external modules, but only a specific few are provided and supported by VMware. Additional,... |
|
V-256653
|
Medium |
VAMI server binaries and libraries must be verified for their integrity. |
Being able to verify that a patch, upgrade, certificate, etc., being added to the web server is unchanged from the producer of the file is essential for file validation and nonrepudiation of the information.
VMware delivers product updates and patches regularly. When VAMI is updated, the signed packages will also... |
|
V-256652
|
Medium |
The rsyslog must be configured to monitor VAMI logs. |
For performance reasons, rsyslog file monitoring is preferred over configuring VAMI to send events to a syslog facility. Without ensuring that logs are created, rsyslog configs are created, and those configs are loaded, the log file monitoring and shipping will not be effective.
VAMI syslog configuration is included by default... |
|
V-256651
|
Medium |
VAMI log files must only be accessible by privileged users. |
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.
In addition, access to log records provides information an attacker could use... |
|
V-256650
|
Medium |
VAMI must produce log records containing sufficient information to establish what type of events occurred. |
After a security incident has occurred, investigators will often review log files to determine what happened. Understanding what type of event occurred is critical for investigation of a suspicious event.
Satisfies: SRG-APP-000095-WSR-000056, SRG-APP-000096-WSR-000057, SRG-APP-000097-WSR-000058, SRG-APP-000098-WSR-000059, SRG-APP-000099-WSR-000061, SRG-APP-000100-WSR-000064, SRG-APP-000374-WSR-000172, SRG-APP-000375-WSR-000171 |
|
V-256649
|
Medium |
VAMI 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-256648
|
Medium |
VAMI must be configured to monitor 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.
VAMI uses the "mod_accesslog" module to log information relating to remote requests. These logs can then be piped... |
|
V-256647
|
Medium |
VAMI must use cryptography to protect the integrity of remote sessions. |
Data exchanged between the user and the web server can range from static display data to credentials used to log in the hosted application. Even when data appears to be static, the nondisplayed logic in a web page may expose business logic or trusted system relationships. The integrity of all... |
|
V-256645
|
Medium |
VAMI must limit the number of simultaneous requests. |
|
