CVE Vulnerabilities

CVE-2016-0762

Observable Discrepancy

Published: Aug 10, 2017 | Modified: Dec 08, 2023
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
2.6 LOW
AV:N/AC:H/Au:N/C:P/I:N/A:N
RedHat/V3
3.7 LOW
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Ubuntu
LOW

The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not process the supplied password if the supplied user name did not exist. This made a timing attack possible to determine valid user names. Note that the default configuration includes the LockOutRealm which makes exploitation of this vulnerability harder.

Weakness

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

Affected Software

Name Vendor Start Version End Version
Tomcat Apache 6.0.0 (including) 6.0.45 (including)
Tomcat Apache 7.0.0 (including) 7.0.70 (including)
Tomcat Apache 8.0 (including) 8.0.36 (including)
Tomcat Apache 8.5.0 (including) 8.5.4 (including)
Tomcat Apache 9.0.0-milestone1 (including) 9.0.0-milestone1 (including)
Tomcat Apache 9.0.0-milestone2 (including) 9.0.0-milestone2 (including)
Tomcat Apache 9.0.0-milestone3 (including) 9.0.0-milestone3 (including)
Tomcat Apache 9.0.0-milestone4 (including) 9.0.0-milestone4 (including)
Tomcat Apache 9.0.0-milestone5 (including) 9.0.0-milestone5 (including)
Tomcat Apache 9.0.0-milestone6 (including) 9.0.0-milestone6 (including)
Tomcat Apache 9.0.0-milestone7 (including) 9.0.0-milestone7 (including)
Tomcat Apache 9.0.0-milestone8 (including) 9.0.0-milestone8 (including)
Tomcat Apache 9.0.0-milestone9 (including) 9.0.0-milestone9 (including)
Red Hat Enterprise Linux 7 RedHat tomcat-0:7.0.76-2.el7 *
Red Hat JBoss Web Server 3.1 RedHat *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat hibernate4-eap6-0:4.2.23-1.Final_redhat_1.1.ep6.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat jbcs-httpd24-0:1-3.jbcs.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat jbcs-httpd24-apache-commons-daemon-0:1.0.15-1.redhat_2.1.jbcs.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat jbcs-httpd24-apache-commons-daemon-jsvc-1:1.0.15-17.redhat_2.jbcs.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat mod_cluster-0:1.3.5-2.Final_redhat_2.1.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat7-0:7.0.70-16.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat8-0:8.0.36-17.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat-native-0:1.2.8-9.redhat_9.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat hibernate4-eap6-0:4.2.23-1.Final_redhat_1.1.ep6.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat jbcs-httpd24-0:1-3.jbcs.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat jbcs-httpd24-apache-commons-daemon-0:1.0.15-1.redhat_2.1.jbcs.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat jbcs-httpd24-apache-commons-daemon-jsvc-1:1.0.15-17.redhat_2.jbcs.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat mod_cluster-0:1.3.5-2.Final_redhat_2.1.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat7-0:7.0.70-16.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat8-0:8.0.36-17.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat-native-0:1.2.8-9.redhat_9.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat-vault-0:1.0.8-9.Final_redhat_2.1.ep7.el7 *
Tomcat6 Ubuntu precise *
Tomcat6 Ubuntu trusty *
Tomcat6 Ubuntu upstream *
Tomcat6 Ubuntu xenial *
Tomcat7 Ubuntu artful *
Tomcat7 Ubuntu precise *
Tomcat7 Ubuntu upstream *
Tomcat7 Ubuntu xenial *
Tomcat7 Ubuntu yakkety *
Tomcat7 Ubuntu zesty *
Tomcat8 Ubuntu upstream *
Tomcat8 Ubuntu xenial *

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

References