What is the CVSS score of CVE-2022-23302?

CVE-2022-23302 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.8%.

Is there a patch available for CVE-2022-23302?

Yes, a patch is available for CVE-2022-23302. Update the affected software to the latest version immediately.

Log4J CVE-2022-23302

HIGH

Deserialization of Untrusted Data (CWE-502)

2022-01-18 security@apache.org

RCE Deserialization Apache Log4J Snapmanager Brocade Sannav Reload4J Advanced Supply Chain Planning Business Intelligence Business Process Management Suite Communications Eagle Ftp Table Base Retrieval Communications Instant Messaging Server Communications Messaging Server Communications Network Integrity Communications Offline Mediation Controller Communications Unified Inventory Management E Business Suite Cloud Manager And Cloud Backup Module Enterprise Manager Base Platform Financial Services Revenue Management And Billing Analytics Healthcare Foundation Hyperion Data Relationship Management Hyperion Infrastructure Technology Identity Management Suite Identity Manager Connector Jdeveloper Middleware Common Libraries And Tools Mysql Enterprise Monitor Tuxedo Weblogic Server

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jan 18, 2022 - 16:15 cve.org

HIGH 8.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

30,810 maven packages depend on log4j:log4j (7,820 direct, 23,828 indirect)
1 maven packages depend on org.zenframework.z8.dependencies.commons:log4j-1.2.17 (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.2.17 and other introduced versions.

DescriptionCVE.org

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.

AnalysisAI

Technical ContextAI

This vulnerability is classified as Deserialization of Untrusted Data (CWE-502), which allows attackers to execute arbitrary code through malicious serialized objects. 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. Affected products include: Apache Log4J, Netapp Snapmanager, Broadcom Brocade Sannav, Qos Reload4J, Oracle Advanced Supply Chain Planning.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Avoid deserializing untrusted data. Use safe serialization formats (JSON). Implement integrity checks and type allowlists.