Skip to content

Improper Verification of Source of a Communication Channel in Apache Tomcat

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

Package

maven org.apache.tomcat:tomcat (Maven)

Affected versions

>= 7.0.0, < 7.0.68
>= 8.0.0, < 8.0.32
>= 9.0.0M1, <= 9.0.0.M2

Patched versions

7.0.68
8.0.32
9.0.0.M3

Description

The setGlobalContext method in org/apache/naming/factory/ResourceLinkFactory.java in Apache Tomcat 7.x before 7.0.68, 8.x before 8.0.31, and 9.x before 9.0.0.M3 does not consider whether ResourceLinkFactory.setGlobalContext callers are authorized, which allows remote authenticated users to bypass intended SecurityManager restrictions and read or write to arbitrary application data, or cause a denial of service (application disruption), via a web application that sets a crafted global context.

References

Published by the National Vulnerability Database Feb 25, 2016
Published to the GitHub Advisory Database May 14, 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
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS score

0.129%
(49th percentile)

Weaknesses

CVE ID

CVE-2016-0763

GHSA ID

GHSA-9hjv-9h75-xmpp

Source code

Credits

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