Deserialization of Untrusted Data Affecting eap7-infinispan-core package, versions <0:8.2.11-1.SP2_redhat_00001.1.ep7.el7


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
7.63% (95th 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 Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-EAP7INFINISPANCORE-7833520
  • published26 Aug 2024
  • disclosed18 Jan 2022

Introduced: 18 Jan 2022

CVE-2022-23302  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade RHEL:7 eap7-infinispan-core to version 0:8.2.11-1.SP2_redhat_00001.1.ep7.el7 or higher.
This issue was patched in RHSA-2024:5856.

NVD Description

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

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

CVSS Scores

version 3.1