Homepage

Insecure Default Initialization of Resource Affecting tomcat-jsp-2.2-api package, versions <0:7.0.76-10.amzn2.0.1

Severity

 Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
14.81% (96th 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 IDSNYK-AMZN2-TOMCATJSP22API-1678624
  • published27 Sept 2021
  • disclosed16 May 2018
Report a new vulnerability Found a mistake?

Introduced: 16 May 2018

CVE-2018-8014  (opens in a new tab)
CWE-1188  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 tomcat-jsp-2.2-api to version 0:7.0.76-10.amzn2.0.1 or higher.
This issue was patched in ALAS2-2020-1402.

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 Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue.

References