Sensitive Information Uncleared Before Release Affecting tomcat6-log4j package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.61% (80th 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-2824866
  • published13 May 2022
  • disclosed12 May 2022

Introduced: 12 May 2022

CVE-2022-25762  (opens in a new tab)
CWE-226  (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 a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.

CVSS Scores

version 3.1