发布时间: 2022年2月11日
修改时间: 2024年10月31日
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.
| NVD | openEuler | |
|---|---|---|
| Confidentiality | High | High |
| Attack Vector | Network | Network |
| CVSS评分 | 8.8 | 8.8 |
| Attack Complexity | Low | Low |
| Privileges Required | Low | Low |
| Scope | Unchanged | Unchanged |
| Integrity | High | High |
| User Interaction | None | None |
| Availability | High | High |
| 公告名 | 概要 | 发布时间 |
|---|---|---|
| KylinSec-SA-2022-1028 | log4j12 security update | 2022年2月11日 |
| KylinSec-SA-2022-2627 | log4j12 security update | 2022年11月11日 |
| 产品 | 包 | 状态 |
|---|---|---|
| KY3.4-4A | log4j12 | Fixed |
| KY3.4-5A | log4j12 | Fixed |
| KY3.5.1 | log4j12 | Fixed |
