cis-tomcat9-v120-2-4

name	cis-tomcat9-v120-2.4
description	Disable X-Powered-By HTTP Header and Rename the Server Value for all Connectors (Automated)
category	cis-tomcat
version	1.2.0
author	cyberstrike-official
tags	["cis","tomcat","linux","java","information-leakage","server-info"]
cis_id	2.4
cis_benchmark	CIS Apache Tomcat 9 Benchmark v1.2.0
tech_stack	["linux","tomcat","java"]
cwe_ids	[]
chains_with	[]
prerequisites	[]
severity_boost	{}

Disable X-Powered-By HTTP Header and Rename the Server Value for all Connectors (Automated)

Description

The xpoweredBy setting determines if Apache Tomcat will advertise its presence via the X-Powered-By HTTP header. It is recommended that this value be set to false. The server attribute overrides the default value that is sent down in the HTTP header further masking Apache Tomcat.

Rationale

Preventing Tomcat from advertising its presence in this manner may increase the complexity for attackers to determine which vulnerabilities affect the server platform.

Audit Procedure

Perform the following to determine if the server platform, as advertised in the HTTP Server header, has been changed:

1. Locate all Connector elements in $CATALINA_HOME/conf/server.xml.
2. Ensure each Connector that has the xpoweredBy attribute does NOT have it set to true.

Remediation

Perform the following to prevent Tomcat from advertising its presence via the X-PoweredBy HTTP header.

1. Add the xpoweredBy attribute to each Connector specified in $CATALINA_HOME/conf/server.xml. Set the xpoweredBy attributes value to false.

<Connector
...
xpoweredBy="false" />

Alternatively, ensure the xpoweredBy attribute for each Connector specified in $CATALINA_HOME/conf/server.xml is absent.

2. Add the server attribute to each Connector specified in $CATALINA_HOME/conf/server.xml. Set the server attribute value to anything except a blank string.

Default Value

The default value is false.

References

1. https://tomcat.apache.org/tomcat-9.0-doc/config/http.html

CIS Controls

v8:

• 16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • Use standard, industry-recommended hardening configuration templates for application infrastructure components. This includes underlying servers, databases, and web servers, and applies to cloud containers, Platform as a Service (PaaS) components, and SaaS components. Do not allow in-house developed software to weaken configuration hardening.