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

EPSS
3.22% (87th 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-9872789
  • published28 Apr 2025
  • disclosed1 Jan 2010

Introduced: 1 Jan 2010

CVE-2010-0434  (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.

The ap_read_request function in server/protocol.c in the Apache HTTP Server 2.2.x before 2.2.15, when a multithreaded MPM is used, does not properly handle headers in subrequests in certain circumstances involving a parent request that has a body, which might allow remote attackers to obtain sensitive information via a crafted request that triggers access to memory locations associated with an earlier request.

References

CVSS Base Scores

version 3.1