Information Exposure Affecting log4j package, versions <0:1.2.12-1jpp_1rh


Severity

Recommended
low

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
69.41% (99th 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-RHEL10-LOG4J-9881823
  • published28 Apr 2025
  • disclosed14 Aug 2007

Introduced: 14 Aug 2007

CVE-2007-3385  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade RHEL:10 log4j to version 0:1.2.12-1jpp_1rh or higher.
This issue was patched in RHSA-2010:0602.

NVD Description

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

Apache Tomcat 6.0.0 to 6.0.13, 5.5.0 to 5.5.24, 5.0.0 to 5.0.30, 4.1.0 to 4.1.36, and 3.3 to 3.3.2 does not properly handle the &#34; character sequence in a cookie value, which might cause sensitive information such as session IDs to be leaked to remote attackers and enable session hijacking attacks.

References

CVSS Base Scores

version 3.1