Skip to content

Observable Discrepancy in Apache Tomcat

Moderate severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Feb 22, 2024

Package

maven org.apache.tomcat:tomcat (Maven)

Affected versions

>= 9.0.0M1, <= 9.0.0.M9
>= 8.5.0, <= 8.5.4
>= 8.0.0.RC1, <= 8.0.36
>= 7.0.0, < 7.0.72
>= 6.0.0, <= 6.0.45

Patched versions

9.0.0.M10
8.5.5
8.0.37
7.0.72
6.0.46

Description

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.

References

Published by the National Vulnerability Database Aug 10, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 6, 2022
Last updated Feb 22, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.132%
(50th percentile)

Weaknesses

CVE ID

CVE-2016-0762

GHSA ID

GHSA-wxcp-f2c8-x6xv

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.