Information Exposure Affecting tomcat6-log4j package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.11% (46th 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-1355190
  • published26 Jul 2021
  • disclosed27 Oct 2016

Introduced: 27 Oct 2016

CVE-2016-6794  (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.

When a SecurityManager is configured, a web application's ability to read system properties should be controlled by the SecurityManager. In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70, 6.0.0 to 6.0.45 the system property replacement feature for configuration files could be used by a malicious web application to bypass the SecurityManager and read system properties that should not be visible.

References

CVSS Scores

version 3.1