Skip to content

Exposure of Resource to Wrong Sphere in Apache Tomcat

Critical severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Apr 18, 2024

Package

maven org.apache.tomcat.embed:tomcat-embed-core (Maven)

Affected versions

>= 9.0.0.M1, <= 9.0.0.M17
>= 8.5.0, <= 8.5.12
>= 8.0.0, <= 8.0.41
>= 7.0.0, <= 7.0.75

Patched versions

9.0.0.M18
8.5.13
8.0.42
7.0.76
maven org.apache.tomcat:tomcat-catalina (Maven)
>= 9.0.0.M1, <= 9.0.0.M17
>= 8.5.0, <= 8.5.12
>= 8.0.0, <= 8.0.41
>= 7.0.0, <= 7.0.75
9.0.0.M18
8.5.13
8.0.42
7.0.76

Description

While investigating bug 60718, it was noticed that some calls to application listeners in Apache Tomcat 9.0.0.M1 to 9.0.0.M17, 8.5.0 to 8.5.11, 8.0.0.RC1 to 8.0.41, and 7.0.0 to 7.0.75 did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application.

References

Published by the National Vulnerability Database Apr 17, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 1, 2022
Last updated Apr 18, 2024

Severity

Critical

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.356%
(73rd percentile)

Weaknesses

CVE ID

CVE-2017-5648

GHSA ID

GHSA-3vx3-xf6q-r5xp

Source code

Credits

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