| Finding ID |
Severity |
Title |
Description |
|
V-214359
|
High |
The Apache web server software must be a vendor-supported version. |
Many vulnerabilities are associated with older versions of web server software. As hot fixes and patches are issued, these solutions are included in the next version of the server software. Maintaining the web server at a current version makes the efforts of a malicious user to exploit the web service... |
|
V-214357
|
High |
All accounts installed with the Apache web server software and tools must have passwords assigned and default passwords changed. |
During installation of the Apache web server software, accounts are created for the Apache web server to operate properly. The accounts installed can have either no password installed or a default password, which will be known and documented by the vendor and the user community.
The first things an attacker... |
|
V-214322
|
High |
Apache web server application directories, libraries, and configuration files must only be accessible to privileged users. |
When accounts used for web server features such as documentation, sample code, example applications, tutorials, utilities, and services are created even though the feature is not installed, they become an exploitable threat to a web server.
These accounts become inactive, are not monitored through regular use, and passwords for the... |
|
V-214321
|
High |
The Apache web server must provide install options to exclude the installation of documentation, sample code, example applications, and tutorials. |
Web server documentation, sample code, example applications, and tutorials may be an exploitable threat to a web server because this type of code has not been evaluated and approved. A production web server must only contain components that are operationally necessary (e.g., compiled code, scripts, web-content, etc.).
Any documentation, sample... |
|
V-214360
|
Medium |
The Apache web server must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without this notification, the security personnel may be unaware of an impending failure of the audit capability and system operation may be adversely affected.
Audit processing... |
|
V-214356
|
Medium |
The Apache web server must install security-relevant software updates within the configured time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). |
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous... |
|
V-214355
|
Medium |
The Apache web server cookies, such as session cookies, sent to the client using SSL/TLS must not be compressed. |
A cookie is used when a web server needs to share data with the client's browser. The data is often used to remember the client when the client returns to the hosted application at a later date. A session cookie is a special type of cookie used to remember the... |
|
V-214354
|
Medium |
The Apache web server must be tuned to handle the operational requirements of the hosted application. |
A denial of service (DoS) can occur when the Apache web server is so overwhelmed that it can no longer respond to additional requests. A web server not properly tuned may become overwhelmed and cause a DoS condition even with expected traffic from users. To avoid a DoS, the Apache... |
|
V-214353
|
Medium |
The Apache web server must be protected from being stopped by a non-privileged user. |
An attacker has at least two reasons to stop a web server. The first is to cause a denial of service (DoS), and the second is to put in place changes the attacker made to the web server configuration.
To prohibit an attacker from stopping the Apache web server, the... |
|
V-214352
|
Medium |
The Apache web server must only accept client certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs). |
Non-DoD-approved PKIs have not been evaluated to ensure they have security controls and identity vetting procedures in place that are sufficient for DoD systems to rely on the identity asserted in the certificate. PKIs lacking sufficient security controls and identity vetting procedures risk being compromised and issuing certificates that enable... |
|
V-214351
|
Medium |
The Apache web server must generate log records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) with a minimum granularity of one second. |
If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis across multiple devices and log records.
Time stamps generated by the Apache web server include date and time. Time is commonly expressed in UTC, a modern continuation of GMT,... |
|
V-214350
|
Medium |
The Apache web server must use a logging mechanism that is configured to provide a warning to the Information System Security Officer (ISSO) and System Administrator (SA) when allocated record storage volume reaches 75 percent of maximum log record storage capacity. |
It is critical for the appropriate personnel to be aware if a system is at risk of failing to process logs as required. Log processing failures include software/hardware errors, failures in the log capturing mechanisms, and log storage capacity being reached or exceeded.
If log capacity were to be exceeded,... |
|
V-214349
|
Medium |
The Apache web server must be configurable to integrate with an organizations security infrastructure. |
A web server will typically use logging mechanisms for maintaining a historical log of activity that occurs within a hosted application. 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.
While it is important... |
|
V-214348
|
Medium |
The Apache web server must not impede the ability to write specified log record content to an audit log server. |
Writing events to a centralized management audit system offers many benefits to the enterprise over having dispersed logs. Centralized management of audit records and logs provides for efficiency in maintenance and management of records, enterprise analysis of events, and backup and archiving of event records enterprise-wide. The web server and... |
|
V-214347
|
Medium |
The Apache web server must use a logging mechanism that is configured to allocate log record storage capacity large enough to accommodate the logging requirements of the Apache web server. |
To make certain that the logging mechanism used by the web server has sufficient storage capacity in which to write the logs, the logging mechanism needs to be able to allocate log record storage capacity.
The task of allocating log record storage capacity is usually performed during initial installation of... |
|
V-214346
|
Medium |
An Apache web server that is part of a web server cluster must route all remote management through a centrally managed access control point. |
A web server cluster is a group of independent Apache web servers that are managed as a single system for higher availability, easier manageability, and greater scalability. Without having centralized control of the web server cluster, management of the cluster becomes difficult. It is critical that remote management of the... |
|
V-214345
|
Medium |
Non-privileged accounts on the hosting system must only access Apache web server security-relevant information and functions through a distinct administrative account. |
By separating Apache web server security functions from non-privileged users, roles can be developed that can then be used to administer the Apache web server. Forcing users to change from a non-privileged account to a privileged account when operating on the Apache web server or on security-relevant information forces users... |
|
V-214344
|
Medium |
The Apache web server must be configured to immediately disconnect or disable remote access to the hosted applications. |
During an attack on the Apache web server or any of the hosted applications, the system administrator may need to disconnect or disable access by users to stop the attack.
The Apache web server must be configured to disconnect users to a hosted application without compromising other hosted applications unless... |
|
V-214343
|
Medium |
The Apache web server must restrict inbound connections from nonsecure zones. |
Remote access to the Apache web server is any access that communicates through an external, non-organization-controlled network. Remote access can be used to access hosted applications or to perform management functions.
A web server can be accessed remotely and must be capable of restricting access from what the DoD defines... |
|
V-214342
|
Medium |
The Apache web server must set an inactive timeout for completing the TLS handshake |
Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user.
Timeouts for completing the TLS handshake, receiving the request headers and/or the request body from the client. If the client fails to... |
|
V-214341
|
Medium |
The Apache web server must set an absolute timeout for sessions. |
Leaving sessions open indefinitely is a major security risk. An attacker can easily use an already authenticated session to access the hosted application as the previously authenticated user. By closing sessions after an absolute period of time, the user is forced to reauthenticate, guaranteeing the session is still in use.... |
|
V-214340
|
Medium |
Debugging and trace information used to diagnose the Apache web server must be 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-214339
|
Medium |
Warning and error messages displayed to clients must be modified to minimize the identity of the Apache web server, patches, loaded modules, and directory paths. |
Information needed by an attacker to begin looking for possible vulnerabilities in a web server includes any information about the web server, backend systems being accessed, and plug-ins or modules being used.
Web servers will often display error messages to client users, displaying enough information to aid in the debugging... |
|
V-214338
|
Medium |
The Apache web server must restrict the ability of users to launch denial-of-service (DoS) attacks against other information systems or networks. |
Apache web server can limit the ability of the web server being used in a DoS attack through several methods. The methods employed will depend upon the hosted applications and their resource needs for proper operation.
An example setting that could be used to limit the ability of the web... |
|
V-214337
|
Medium |
The Apache web server document directory must be in a separate partition from the Apache web servers system files. |
A web server is used to deliver content on the request of a client. The content delivered to a client must be controlled, allowing only hosted application files to be accessed and delivered. To allow a client access to system files of any type is a major security risk that... |
|
V-214336
|
Medium |
The Apache web server must be built to 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 DoS for users depends on what type of application the web server is hosting. For an application presenting publicly available information that is not critical, a safe state for failure might be to shut down for any type... |
|
V-214335
|
Medium |
The Apache web server must generate unique session identifiers with definable entropy. |
Generating a session identifier (ID) that is not easily guessed through brute force is essential to deter several types of session attacks. By knowing the session ID, an attacker can hijack a user session that has already been user authenticated by the hosted application. The attacker does not need to... |
|
V-214334
|
Medium |
The Apache web server must generate unique session identifiers that cannot be reliably reproduced. |
Communication between a client and the Apache web server is done using the HTTP protocol, but HTTP is a stateless protocol. To maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the... |
|
V-214333
|
Medium |
The Apache web server must accept only system-generated session identifiers. |
Communication between a client and the web server is done using the HTTP protocol, but HTTP is a stateless protocol. To maintain a connection or session, a web server will generate a session identifier (ID) for each client session when the session is initiated. The session ID allows the web... |
|
V-214332
|
Medium |
Cookies exchanged between the Apache web server and client, such as session cookies, must have security settings that disallow cookie access outside the originating Apache web server and hosted application. |
Cookies are used to exchange data between the web server and the client. Cookies, such as a session cookie, may contain session information and user credentials used to maintain a persistent connection between the user and the hosted application since HTTP/HTTPS is a stateless protocol.
When the cookie parameters are... |
|
V-214331
|
Medium |
The Apache web server must invalidate session identifiers upon hosted application user logout or other session termination. |
Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries from capturing and continuing to employ previously valid session IDs.
Session IDs are tokens generated by web applications to uniquely identify an application user's session. Unique session IDs help to reduce predictability of said identifiers.... |
|
V-214330
|
Medium |
The Apache web server must separate the hosted applications from hosted Apache web server management functionality. |
The separation of user functionality from web server management can be accomplished by moving management functions to a separate IP address or port. To further separate the management functions, separate authentication methods and certificates should be used.
By moving the management functionality, the possibility of accidental discovery of the management... |
|
V-214329
|
Medium |
Apache web server accounts accessing the directory tree, the shell, or other operating system functions and utilities must only be administrative accounts. |
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 be closely monitored and controlled. Only the... |
|
V-214328
|
Medium |
The Apache web server must perform RFC 5280-compliant certification path validation. |
A certificate's certification path is the path from the end entity certificate to a trusted root certification authority (CA). Certification path validation is necessary for a relying party to make an informed decision regarding acceptance of an end entity certificate. Certification path validation includes checks such as certificate issuer trust,... |
|
V-214327
|
Medium |
The Apache web server must encrypt passwords during transmission. |
Data used to authenticate, especially passwords, needs to be protected at all times, and encryption is the standard method for protecting authentication data during transmission. Data used to authenticate can be passed to and from the web server for many reasons.
Examples include data passed from a user to the... |
|
V-214326
|
Medium |
The Apache web server must be configured to use a specified IP address and port. |
The web server must be configured to listen on a specified IP address and port. Without specifying an IP address and port for the web server to use, the web server will listen on all IP addresses available to the hosting server. If the web server has multiple IP addresses,... |
|
V-214325
|
Medium |
The Apache web server must have Web Distributed Authoring (WebDAV) disabled. |
A web server can be installed with functionality that, just 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... |
|
V-214324
|
Medium |
The Apache web server must allow the mappings to unused and vulnerable scripts to be removed. |
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-214323
|
Medium |
The Apache web server 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-214320
|
Medium |
The Apache web server must not be a proxy server. |
A web server should be primarily a web server or a proxy server but not both, for the same reasons that other multiuse servers are not recommended. Scanning for web servers that will also proxy requests into an otherwise protected network is a very common attack, making the attack anonymous. |
|
V-214319
|
Medium |
The Apache web server must only contain services and functions necessary for operation. |
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.
The web server must provide the capability to disable, uninstall, or deactivate functionality and services that are deemed to be non-essential to the... |
|
V-214318
|
Medium |
The Apache web server must not perform user management for hosted applications. |
User management and authentication can be an essential part of any application hosted by the web server. Along with authenticating users, the user management function must perform several other tasks such as password complexity, locking users after a configurable number of failed logons, and management of temporary and emergency accounts.... |
|
V-214316
|
Medium |
The log data and records from the Apache web server must be backed up onto a different system or media. |
Protection of log data includes ensuring log data is not accidentally lost or deleted. Backing up log records to an unrelated system or onto separate media than the system the web server is actually running on helps to ensure that, in the event of a catastrophic system failure, the log... |
|
V-214315
|
Medium |
The log information from the Apache web server must be protected from unauthorized deletion and modification. |
Log data is essential in the investigation of events. The accuracy of the information is always pertinent. Information that is not accurate does not help in the revealing of potential security risks and may hinder the early discovery of a system compromise. One of the first steps an attacker will... |
|
V-214314
|
Medium |
The Apache web server 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 potentially... |
|
V-214313
|
Medium |
The Apache web server must use a logging mechanism that is configured to alert the (ISSO) and System Administrator (SA) in the event of a processing failure. |
Reviewing log data allows an investigator to recreate the path of an attacker and to capture forensic data for later use. Log data is also essential to system administrators in their daily administrative duties on the hosted system or within the hosted applications.
If the logging system begins to fail,... |
|
V-214312
|
Medium |
An Apache web server, behind a load balancer or proxy server, must produce log records containing the client IP information as the source and destination and not the load balancer or proxy IP information with each event. |
Apache web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined.
Ascertaining the correct source, e.g., source IP, of the events is important during forensic analysis. Correctly determining the source will add information to the overall... |
|
V-214311
|
Medium |
The Apache web server must produce log records containing sufficient information to establish what type of events occurred. |
Web server logging capability is critical for accurate forensic analysis. Without sufficient and accurate information, a correct replay of the events cannot be determined.
Ascertaining the correct type of event that occurred is important during forensic analysis. The correct determination of the event and when it occurred is important in... |
|
V-214310
|
Medium |
The Apache web server must generate, at a minimum, log records for system startup and shutdown, system access, and system authentication events. |
Log records can be generated from various components within the Apache web server (e.g., httpd, plug-ins to external backends, etc.). From a web server perspective, certain specific Apache web server functionalities may be logged as well. The Apache web server must allow the definition of what events are to be... |
|
V-214309
|
Medium |
System logging must be enabled. |
The server error logs are invaluable because they can also be used to identify potential problems and enable proactive remediation. Log data can reveal anomalous behavior such as "not found" or "unauthorized" errors that may be an evidence of attack attempts. Failure to enable error logging can significantly reduce the... |
|
V-214308
|
Medium |
The Apache web server must use encryption strength in accordance with the categorization of data hosted by the Apache web server when remote connections are provided. |
The Apache web server has several remote communications channels. Examples are user requests via http/https, communication to a backend database, and communication to authenticate users. The encryption used to communicate must match the data that is being retrieved or presented.
Methods of communication are "http" for publicly displayed information, "https"... |
|
V-214307
|
Medium |
The Apache web server must perform server-side session management. |
Session management is the practice of protecting the bulk of the user authorization and identity information. Storing of this data can occur on the client system or on the server.
When the session information is stored on the client, the session ID, along with the user authorization and identity information,... |
|
V-214306
|
Medium |
The Apache web server must limit the number of allowed simultaneous session requests. |
Apache web server management includes the ability to control the number of users and user sessions that utilize an Apache web server. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to several types of denial-of-service (DoS) attacks.
Although there is some latitude... |
|
V-214358
|
Low |
The Apache web server must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
Configuring the Apache web server to implement organization-wide security implementation guides and security checklists guarantees compliance with federal standards and establishes a common security baseline across the DoD that reflects the most restrictive security posture consistent with operational requirements.
Configuration settings are the set of parameters that can be changed... |
