Title

Tomcat must generate log records when successful/unsuccessful attempts to access subject privileges occur. (Cat II impact)

Discussion

Accessing a subject's privileges can be used to elevate a lower-privileged subject's privileges temporarily in order to cause harm to the application server or to gain privileges to operate temporarily for a designed purpose. When these actions take place, the event needs to be logged. Application servers either provide a local user store, or they integrate with enterprise user stores like LDAP. When the application server provides the user store and enforces authentication, the application server must generate a log record when modification of privileges is successfully or unsuccessfully performed.

Check Content

Review the logging.properties file for manager logging to determine if the server generates log records when successful/unsuccessful attempts are made to access privileges. The following lines are an example of manager logging enabled: 3manager.org.apache.juli.FileHandler.level = FINE 3manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs 3manager.org.apache.juli.FileHandler.prefix = manager 3manager.org.apache.juli.FileHandler.rotatable = false If these lines do not exist or are commented out, this is a finding.

Fix Text

Configure the Tomcat server to generate log records when privileges are successfully/unsuccessfully accessed.

Additional Identifiers

Rule ID: SV-46430r3_rule

Vulnerability ID: V-35143

Group Title:

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.