Information Exposure Affecting tomcat6-log4j package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.1% (43rd 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-RHEL6-TOMCAT6LOG4J-1406580
  • published26 Jul 2021
  • disclosed12 Oct 2020

Introduced: 12 Oct 2020

CVE-2020-13943  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:6 tomcat6-log4j.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat6-log4j package and not the tomcat6-log4j package as distributed by RHEL. See How to fix? for RHEL:6 relevant fixed versions and status.

If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.

CVSS Scores

version 3.1