An Apache web server using mobile code must meet DoD-defined mobile code requirements.
From Apache Server 2.4 UNIX Site Security Technical Implementation Guide
Part of SRG-APP-000206-WSR-000128
Associated with:
CCI-001166
AS24-U2-000420_rule
An Apache web server using mobile code must meet DoD-defined mobile code requirements.
Vulnerability discussion
Mobile code in hosted applications allows the developer to add functionality and displays to hosted applications that are fluid, as opposed to a static web page. The data presentation becomes more appealing to the user and is easier to analyze, and navigation through the hosted application and data is much less complicated. Some mobile code technologies in use in today's applications are Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. The DoD has created policies that define the usage of mobile code on DoD systems. The usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations. The web server may host applications that contain mobile code and therefore must meet the DoD-defined requirements regarding the deployment and/or use of mobile code. This includes digitally signing applets provide a means for the client to establish application authenticity.
Check content
In a command line, run "httpd -M | grep -i ssl_module".
If the "ssl_module" is not enabled, this is a finding.
Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file:
# httpd -V | egrep -i 'httpd_root|server_config_file'
-D HTTPD_ROOT="/etc/httpd"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
Search for the directive "SSLProtocol" in the "httpd.conf" file:
# cat //httpd.conf | grep -i "SSLProtocol"
If the "SSLProtocol" directive is missing or does not look like the following, this is a finding:
SSLProtocol -ALL +TLSv1.2
If the TLS version is not TLS 1.2 or higher, according to NIST SP 800-52 Rev 2, or if non-FIPS-approved algorithms are enabled, this is a finding.
NOTE: In some cases, web servers are configured in an environment to support load balancing. This configuration most likely uses a content switch to control traffic to the various web servers. In this situation, the TLS certificate for the websites may be installed on the content switch versus the individual websites. This solution is acceptable as long as the web servers are isolated from the general population LAN. Users should not have the ability to bypass the content switch to access the websites.
Fix text
Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file:
# httpd -V | egrep -i 'httpd_root|server_config_file'
-D HTTPD_ROOT="/etc/httpd"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
Ensure the "SSLProtocol" is added and looks like the following:
SSLProtocol -ALL +TLSv1.2
Restart Apache: apachectl restart
Pro Tips
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer