Homepage

Improper Access Control Affecting tomcat-jsp-2.2-api package, versions <0:7.0.76-9.el7

Severity

 Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.12% (48th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Access Control vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-TOMCATJSP22API-4955191
  • published26 Jul 2021
  • disclosed23 Feb 2018
Report a new vulnerability Found a mistake?

Introduced: 23 Feb 2018

CVE-2018-1305  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade RHEL:7 tomcat-jsp-2.2-api to version 0:7.0.76-9.el7 or higher.
This issue was patched in RHSA-2019:2205.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat-jsp-2.2-api package and not the tomcat-jsp-2.2-api package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.

References