| Finding ID |
Severity |
Title |
Description |
|
V-250341
|
High |
Application security must be enabled on the WebSphere Liberty Server. |
Application security enables security for the applications in the environment. This type of security provides application isolation and requirements for authenticating application users. When a user enables security, both administrative and application security is enabled.
Application security is in effect only when administrative security is enabled via the security feature.... |
|
V-250339
|
High |
The WebSphere Liberty Server must use FIPS 140-2 approved encryption modules when authenticating users and processes. |
Application servers must use and meet requirements of the DoD Enterprise PKI infrastructure for application authentication. Encryption is only as good as the encryption modules used. Unapproved cryptographic module algorithms cannot be verified and cannot be relied upon to provide confidentiality or integrity, and DoD data may be compromised due... |
|
V-250337
|
High |
The WebSphere Liberty Server must use TLS-enabled LDAP. |
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords during transmission. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily compromised.
Application servers have the capability to use either certificates (tokens) or user IDs and passwords... |
|
V-250336
|
High |
The WebSphere Liberty Server must store only encrypted representations of user passwords. |
WebSphere Liberty can either provide a local account store or integrate with enterprise account stores such as LDAP directories. If the application server stores application passwords in the server.xml configuration files, the application server must store encrypted representations of passwords rather than unencrypted, clear-text passwords.
The Liberty Application Server provides... |
|
V-250335
|
High |
Multifactor authentication for network access to privileged accounts must be used. |
Multifactor authentication creates a layered defense and makes it more difficult for an unauthorized person to access the application server. If one factor is compromised or broken, the attacker still has at least one more barrier to breach before successfully breaking into the target. Unlike a simple username/password scenario where... |
|
V-250326
|
High |
Users in the REST API admin role must be authorized. |
Users with console access and OS permissions to the folders where the Liberty Server is installed can make changes to the server. In addition, REST API calls that execute server management tasks are available and can be executed remotely. Adding a user to the admin role will allow that user... |
|
V-250350
|
Medium |
The WebSphere Liberty Server must generate log records for authentication and authorization events. |
Enabling authentication (SECURITY_AUTHN) and authorization (SECURITY_AUTHZ) event handlers configures the server to record security authorization and authentication events. By logging these events, the logs can be analyzed to identify activity that could be related to security events and to aid post mortem forensic analysis.
Satisfies: SRG-APP-000499-AS-000224, SRG-APP-000495-AS-000220, SRG-APP-000503-AS-000228, SRG-APP-000504-AS-000229, SRG-APP-000505-AS-000230,... |
|
V-250349
|
Medium |
The WebSphere Liberty Server must install security-relevant software updates within the time period directed by an authoritative source. |
Security vulnerabilities are often addressed by testing and applying the latest security patches and fix packs. The latest fixpacks can be found at: http://www-01.ibm.com/support/docview.wss?uid=swg27009661 |
|
V-250348
|
Medium |
The WebSphere Liberty Server must be configured to use HTTPS only. |
Transmission of data can take place between the application server and a large number of devices/applications external to the application server. Examples are a web client used by a user, a backend database, a log server, or other application servers in an application server cluster. |
|
V-250347
|
Medium |
The WebSphere Liberty Server must remove all export ciphers to protect the confidentiality and integrity of transmitted information. |
Export grade encryption suites are not strong and do not meet DoD requirements. The encryption for the session becomes easy for the attacker to break. Do not use export grade encryption. |
|
V-250346
|
Medium |
The WebSphere Liberty Server LTPA keys password must be changed. |
The default location of the automatically generated Lightweight Third Party Authentication (LTPA) keys file is ${server.output.dir}/resources/security/ltpa.keys.
The LTPA keys are encrypted with a randomly generated key and a default password of WebAS is initially used to protect the keys. The password is required when importing the LTPA keys into another... |
|
V-250345
|
Medium |
The WebSphere Liberty Server must prohibit the use of cached authenticators after an organization-defined time period. |
Larger authentication cache timeout values can increase security risks. For example, a user who is revoked can still log in by using a credential that is cached in the authentication cache until the cache is refreshed.
Smaller authentication cache timeout values can affect performance. When this value is smaller, the... |
|
V-250344
|
Medium |
The server.xml file must be protected from unauthorized modification. |
When dealing with access restrictions pertaining to change control, it should be noted that any changes to the software, and/or application server configuration could potentially have significant adverse effects on the overall security of the system.
Protect the server.xml file from unauthorized modification by applying file permission restrictions. |
|
V-250343
|
Medium |
The WebSphere Liberty Server must allocate JVM log record storage capacity in accordance with organization-defined log record storage requirements. |
JVM logs are logs used to store application and runtime related events, rather than audit related events. They are mainly used to diagnose application or runtime bugs. However, they are useful for providing more context when correlated with audit related events.
By default, Liberty automatically logs the console.log, messages.log, and... |
|
V-250342
|
Medium |
Users in a reader-role must be authorized. |
The reader role is a management role that allows read-only access to select administrative REST APIs as well as the Admin Center UI (adminCenter-1.0). Preventing non-privileged users from viewing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
Users granted reader... |
|
V-250340
|
Medium |
HTTP session timeout must be configured. |
An attacker can take advantage of user sessions that are left open, thus bypassing the user authentication process.
To thwart the vulnerability of open and unused user sessions, the application server must be configured to close the sessions when a configured condition or trigger event is met.
Session termination terminates... |
|
V-250338
|
Medium |
The WebSphere Liberty Server must use DoD-issued/signed certificates. |
The cornerstone of PKI is the private key used to encrypt or digitally sign information. The key by itself is a cryptographic value that does not contain specific user information, but the key can be mapped to a user. Without mapping the certificate used to authenticate to the user account,... |
|
V-250334
|
Medium |
Basic Authentication must be disabled. |
Basic authentication does not use a centralized user store like LDAP. Not using a centralized user store complicates user management tasks and increases the risk that user accounts could remain on the system long after users have moved to their next deployment. Basic Auth also stores user credentials and passwords... |
|
V-250333
|
Medium |
The WebSphere Liberty Server must use an LDAP user registry. |
To ensure accountability and prevent unauthorized access, application server users must be uniquely identified and authenticated. This is typically accomplished via the use of a user store which is either local (OS-based) or centralized (LDAP) in nature. Best practice guideline to is to use a centralized enterprise LDAP server.
To... |
|
V-250332
|
Medium |
The WebSphere Liberty Server must prohibit or restrict the use of nonsecure ports, protocols, modules, and/or services as defined in the PPSM CAL and vulnerability assessments. |
Some networking protocols may not meet organizational security requirements to protect data and components.
Application servers natively host a number of various features, such as management interfaces, httpd servers, and message queues. These features all run on TCPIP ports. This creates the potential that the vendor may choose to use... |
|
V-250331
|
Medium |
The WebSphere Liberty Server must protect software libraries from unauthorized access. |
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-250330
|
Medium |
The WebSphere Liberty Server must be configured to encrypt log information. |
|
|
V-250329
|
Medium |
The WebSphere Liberty Server must protect log tools from unauthorized access. |
Protecting log data also includes identifying and protecting the tools used to view and manipulate log data. Depending on the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. Therefore, it is imperative that access to... |
|
V-250328
|
Medium |
The WebSphere Liberty Server must protect log information from unauthorized access or changes. |
|
|
V-250327
|
Medium |
The WebSphere Liberty Server must be configured to offload logs to a centralized system. |
Log processing failures include, but are not limited to, failures in the application server log capturing mechanisms or log storage capacity being reached or exceeded. In some instances, it is preferred to send alarms to individuals rather than to an entire group. Application servers must be able to trigger an... |
|
V-250325
|
Medium |
The WebSphere Liberty Server must log remote session and security activity. |
Security auditing must be configured in order to log remote session activity. Security auditing will not be performed unless the audit feature (audit-1.0) has been enabled. The security feature (appSecurity-2.0) must be enabled for the security auditing to capture security transactions. Remote session activity will then be logged, regardless of... |
|
V-250324
|
Medium |
Security cookies must be set to HTTPOnly. |
Web applications use cookies to track users across requests. These cookies, while typically not sensitive in themselves, connect to the existing state on the back-end system. If an intruder were to capture one of these cookies, they could potentially use the cookie to act as the user. Important web traffic... |
|
V-250323
|
Medium |
The WebSphere Liberty Server Quality of Protection (QoP) must be set to use TLSv1.2 or higher. |
Quality of Protection in WebSphere Liberty specifies the security level, ciphers, and mutual authentication settings for the Secure Socket Layer (SSL/TLS) configuration. For Quality of Protection settings to apply, the security feature (appSecurity-2.0) must be defined in order to configure a user registry for the servlet to authenticate against. The... |
|
V-250322
|
Medium |
Maximum in-memory session count must be set according to application requirements. |
Application management includes the ability to control the number of sessions that use an application by all accounts and/or account types. Limiting the number of allowed sessions is helpful in limiting risks related to Denial of Service attacks.
Application servers host and expose business logic and application processes. The application... |
