Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2022-23302— Deserialization of untrusted data in JMSSink in Apache Log4j 1.x

Quick assessment

Affected
Apache Software Foundation Apache Log4j 1.x
Exploitation
High exploitation probability; assess promptly
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Apache Log4j是美国阿帕奇（Apache）基金会的一款基于Java的开源日志记录工具。 Log4j 存在代码问题漏洞，该漏洞源于当攻击者对 Log4j 配置具有写访问权限或配置引用攻击者有权访问的 LDAP 服务时，所有 Log4j 1.x 版本中的 JMSSink 都容易受到不受信任数据的反序列化。 攻击者可以提供一个 TopicConnectionFactoryBindingName 配置，使 JMSSink 执行 JNDI 请求，从而以类似于 CVE-2021-4104 的方式执行远程代码

AI Predicted 8.1 Difficulty: Moderate EPSS 63.56% · P99

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 2

VendorProduct Version RangeStatus
Apache Software Foundation Apache Log4j 1.x 1.0.1< unspecified affected
unspecified< 2.0-alpha1 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-23302

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
可信数据的反序列化
Source: CVE Program / CVE List V5
Vulnerability Title
Apache Log4j 代码问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Apache Log4j是美国阿帕奇（Apache）基金会的一款基于Java的开源日志记录工具。 Log4j 存在代码问题漏洞，该漏洞源于当攻击者对 Log4j 配置具有写访问权限或配置引用攻击者有权访问的 LDAP 服务时，所有 Log4j 1.x 版本中的 JMSSink 都容易受到不受信任数据的反序列化。 攻击者可以提供一个 TopicConnectionFactoryBindingName 配置，使 JMSSink 执行 JNDI 请求，从而以类似于 CVE-2021-4104 的方式执行远程代码
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Apache Software Foundation Apache Log4j 1.x 1.0.1 ~ unspecified -

II. Public POCs for CVE-2022-23302

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-23302

请登录查看更多情报信息。

Vendor Advisories for CVE-2022-23302 (3)

Mailing List Discussions for CVE-2022-23302 (2)

Other References for CVE-2022-23302 (1)

Same Patch Batch · Apache Software Foundation · 2022-01-18 · 3 CVEs total

CVE-2022-23305 SQL injection in JDBC Appender in Apache Log4j V1
CVE-2022-23307 A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code exe

IV. Related Vulnerabilities

Same product: Apache Log4j 1.x
Same vendor: Apache Software Foundation
Same weakness: CWE-502

V. Comments for CVE-2022-23302

No comments yet

Leave a comment