VMware vSphere 6.7 STS Tomcat Security Technical Implementation Guide

Description

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected]

Details

Version / Release: V1R1

Published: 2021-04-15

Updated At: 2021-05-02 21:04:36

Actions

Download

Filter

Findings
Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-239652r679028_rule VCST-67-000001 CCI-000054 MEDIUM The Security Token Service 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 requests. In Tomcat, the "connectionTimeout" attribute sets the
    SV-239653r679031_rule VCST-67-000002 CCI-000054 MEDIUM The Security Token Service 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 sys
    SV-239654r679034_rule VCST-67-000003 CCI-000054 MEDIUM The Security Token Service 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
    SV-239655r679037_rule VCST-67-000004 CCI-000054 MEDIUM The Security Token Service 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 and its applications. When a cookie is tagged with the "Ht
    SV-239656r679251_rule VCST-67-000005 CCI-000067 MEDIUM The Security Token Service 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",
    SV-239657r679043_rule VCST-67-000006 CCI-000169 MEDIUM The Security Token Service must generate log records during Java startup and shutdown. 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 immed
    SV-239658r679046_rule VCST-67-000007 CCI-000163 MEDIUM Security Token Service 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 serv
    SV-239659r679049_rule VCST-67-000008 CCI-001749 MEDIUM The Security Token Service application files must be verified for their integrity. Verifying that the Security Token Service application code is unchanged from its shipping state is essential for file validation and non-repudiation of the Security Token Service. There is no reason the MD5 hash of the rpm original files should be changed
    SV-239660r679052_rule VCST-67-000009 CCI-001749 MEDIUM The Security Token Service must only run one web app. VMware ships the Security Token Service on the VCSA with one web app, in ROOT.war. Any other .war file is potentially malicious and must be removed.
    SV-239661r679055_rule VCST-67-000010 CCI-000381 MEDIUM The Security Token Service must not be configured with unused realms. The Security Token Service performs user authentication at the application level and not through Tomcat. To eliminate unnecessary features and ensure that the Security Token Service remains in its shipping state, the lack of a "UserDatabaseRealm" configur
    SV-239662r679058_rule VCST-67-000011 CCI-000381 MEDIUM The Security Token Service 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 web app attempts to access the listed internal classes d
    SV-239663r679061_rule VCST-67-000012 CCI-000381 MEDIUM The Security Token Service must have Multipurpose Internet Mail Extensions (MIME) that invoke OS shell programs disabled. MIME mappings tell the Security Token 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 "we
    SV-239664r679064_rule VCST-67-000013 CCI-000381 MEDIUM The Security Token Service 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 an
    SV-239665r679067_rule VCST-67-000014 CCI-000381 MEDIUM The Security Token Service 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 a
    SV-239666r679070_rule VCST-67-000015 CCI-000381 MEDIUM The Security Token Service 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, the Security Token Service can continue to consume system resources, which will lead to "OutOfMemoryErrors" when reloading web app
    SV-239667r679073_rule VCST-67-000016 CCI-000381 MEDIUM The Security Token Service 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 application
    SV-239668r679076_rule VCST-67-000017 CCI-001082 MEDIUM The Security Token Service 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. The resources to which these accounts have access must also b
    SV-239669r679079_rule VCST-67-000018 CCI-001190 MEDIUM The Security Token Service 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 the Security Token Service, it is preferable that the service abort startup on any in
    SV-239670r679082_rule VCST-67-000019 CCI-001094 MEDIUM The Security Token Service must limit the number of allowed connections. Limiting the number of established connections to the Security Token Service is a basic denial of service protection. Servers where the limit is too high or unlimited can potentially run out of system resources and negatively affect system availability.
    SV-239671r679085_rule VCST-67-000020 CCI-001310 MEDIUM The Security Token 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 appl
    SV-239672r679088_rule VCST-67-000021 CCI-001310 MEDIUM The Security Token Service 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 appl
    SV-239673r679091_rule VCST-67-000022 CCI-001312 MEDIUM The Security Token Service 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 list
    SV-239674r679094_rule VCST-67-000023 CCI-001312 MEDIUM The Security Token Service 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 list
    SV-239675r679097_rule VCST-67-000024 CCI-001312 MEDIUM The Security Token Service 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 server type, version, patches installed, plug-ins and modul
    SV-239676r679100_rule VCST-67-000025 CCI-001312 MEDIUM The Security Token Service 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 the Security Token Service will ex
    SV-239677r679103_rule VCST-67-000026 CCI-001312 MEDIUM The Security Token Service must have the debug option 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, in
    SV-239678r679106_rule VCST-67-000027 CCI-001348 MEDIUM Rsyslog must be configured to monitor and ship Security Token Service log files. The Security Token Service produces a number of 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 appli
    SV-239679r679109_rule VCST-67-000028 CCI-001762 MEDIUM The Security Token Service 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 the Security Token Service listens on are configur
    SV-239680r679112_rule VCST-67-000029 CCI-002385 MEDIUM The Security Token Service 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 s
    SV-239681r679115_rule VCST-67-000030 CCI-002418 MEDIUM The Security Token Service 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