1. Home
  2. Security Hardening
  3. CIS Apache Tomcat 8 L2 V1.1.0
  4. Do not allow custom header status messages

Do not allow custom header status messages

Details

The ability to specify custom status messages opens up the potential for additional headers to be injected. If custom header status messages are required make sure it is only in US-ASCII and does not include any user-supplied data.

Rationale:

Allowing user-supplied data into a header creates the potential for cross-site scripting (XSS).

Solution

To start Tomcat with USE_CUSTOM_STATUS_MSG_IN_HEADER set to false, add -Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=false to your startup script.

Default Value:

By default this is set to false.

References:

https://tomcat.apache.org/tomcat-8.0-doc/config/systemprops.html

Supportive Information

The following resource is also helpful.

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Unix.

References

Source

Updated on July 16, 2022
Was this article helpful?

Related Articles