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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-435-1 | tomcat6 security update |
![]() |
DSA-3530-1 | tomcat6 security update |
![]() |
DSA-3552-1 | tomcat7 security update |
![]() |
DSA-3609-1 | tomcat8 security update |
![]() |
EUVD-2022-3390 | 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. |
![]() |
GHSA-9hjv-9h75-xmpp | Improper Verification of Source of a Communication Channel in Apache Tomcat |
![]() |
USN-3024-1 | Tomcat vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-05T22:30:04.044Z
Reserved: 2015-12-16T00:00:00
Link: CVE-2016-0763

No data.

Status : Deferred
Published: 2016-02-25T01:59:06.280
Modified: 2025-04-12T10:46:40.837
Link: CVE-2016-0763


No data.