CVE 描述

Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

CVE 信息

相关弱点

CWE-ID	弱点名称	来源
CWE-502	Deserialization of Untrusted Data The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CWE-400	Uncontrolled Resource Consumption The product does not properly control the allocation and maintenance of a limited resource.
CWE-20	Improper Input Validation The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-917	Improper Neutralization of Special Elements used in an Expression Language Statement The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.

指标

指标	评分	严重程度	CVSS 向量	来源
V3.1	10	CRITICAL	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H 更多信息 Base: Exploitabilty Metrics The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack Vector This metric reflects the context by which vulnerability exploitation is possible. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Low Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. None The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack. User Interaction This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component. None The vulnerable system can be exploited without interaction from any user. Base: Scope Metrics The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Changed An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. Base: Impact Metrics The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. Confidentiality Impact This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. High There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. High There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable). Temporal Metrics The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental Metrics These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.	nvd@nist.gov
V2	9.3		AV:N/AC:M/Au:N/C:C/I:C/A:C	nvd@nist.gov

CISA KEV（已知被利用漏洞）

漏洞名称 : Apache Log4j2 Remote Code Execution Vulnerability

必要措施 : For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

已被用于勒索软件攻击活动 : Known

添加日期 : 2021-12-10 00h00 +00:00

截止日期 : 2021-12-24 00h00 +00:00

重要信息

根据 CISA KEV（已知被利用漏洞目录），此 CVE 被认定为存在漏洞且构成活跃威胁。CISA 已将该漏洞列为正被网络犯罪分子积极利用，并强调必须立即采取措施修复。请优先更新和修复此 CVE，以保护系统免遭潜在网络攻击。

EPSS

EPSS 是一种预测漏洞被利用可能性的评分模型。

EPSS 评分

EPSS 模型生成一个介于 0 到 1（即 0% 到 100%）之间的概率评分。评分越高，漏洞被利用的可能性越大。

日期	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2021-12-12	–	15.9%	–	–	–
2021-12-19	–	91.82%	–	–	–
2021-12-26	–	93.28%	–	–	–
2022-01-16	–	93.44%	–	–	–
2022-01-23	–	93.75%	–	–	–
2022-01-30	–	93.9%	–	–	–
2022-02-06	–	–	94.4%	–	–
2022-03-20	–	–	95.1%	–	–
2022-07-17	–	–	90.48%	–	–
2022-11-06	–	–	91.16%	–	–
2022-11-20	–	–	95.47%	–	–
2022-12-11	–	–	97.1%	–	–
2023-03-12	–	–	–	97.58%	–
2023-05-14	–	–	–	97.57%	–
2023-09-24	–	–	–	97.44%	–
2023-10-01	–	–	–	97.47%	–
2023-10-29	–	–	–	97.45%	–
2024-01-07	–	–	–	97.47%	–
2024-02-11	–	–	–	97.56%	–
2024-02-18	–	–	–	97.57%	–
2024-03-17	–	–	–	97.56%	–
2024-06-02	–	–	–	97.56%	–
2024-06-08	–	–	–	97.55%	–
2024-06-23	–	–	–	97.56%	–
2024-07-28	–	–	–	96.98%	–
2024-08-04	–	–	–	96.91%	–
2024-08-25	–	–	–	96.69%	–
2024-09-22	–	–	–	96.49%	–
2024-10-06	–	–	–	96.76%	–
2024-11-17	–	–	–	96.89%	–
2024-12-15	–	–	–	96.88%	–
2024-12-22	–	–	–	97.19%	–
2024-12-29	–	–	–	97.23%	–
2025-01-19	–	–	–	97.23%	–
2025-01-26	–	–	–	97.19%	–
2025-02-02	–	–	–	97.19%	–
2025-02-16	–	–	–	97.1%	–
2025-02-16	–	–	–	97.1%	–
2025-03-02	–	–	–	97.11%	–
2025-03-09	–	–	–	97.11%	–
2025-03-18	–	–	–	–	94.38%
2025-04-15	–	–	–	–	94.48%
2025-04-22	–	–	–	–	94.38%
2025-05-09	–	–	–	–	94.48%
2025-05-10	–	–	–	–	94.38%
2025-05-15	–	–	–	–	94.47%
2025-05-17	–	–	–	–	94.48%
2025-05-18	–	–	–	–	94.38%
2025-06-15	–	–	–	–	94.47%
2025-06-18	–	–	–	–	94.36%
2025-06-26	–	–	–	–	94.47%
2025-06-28	–	–	–	–	94.36%
2025-07-16	–	–	–	–	94.47%
2025-07-21	–	–	–	–	94.36%
2025-08-16	–	–	–	–	94.47%
2025-08-19	–	–	–	–	94.36%
2025-09-09	–	–	–	–	94.47%
2025-09-11	–	–	–	–	94.36%
2025-09-16	–	–	–	–	94.47%
2025-09-19	–	–	–	–	94.36%
2025-10-17	–	–	–	–	94.47%
2025-10-20	–	–	–	–	94.36%
2025-10-29	–	–	–	–	94.47%
2025-11-01	–	–	–	–	94.36%
2025-11-18	–	–	–	–	94.25%
2025-11-21	–	–	–	–	94.45%
2025-11-23	–	–	–	–	94.47%
2025-11-24	–	–	–	–	94.36%
2025-12-18	–	–	–	–	94.45%
2025-12-19	–	–	–	–	94.47%
2025-12-20	–	–	–	–	94.36%
2026-01-18	–	–	–	–	94.47%
2026-01-21	–	–	–	–	94.36%
2026-03-08	–	–	–	–	94.45%
2026-03-15	–	–	–	–	94.36%
2026-03-22	–	–	–	–	94.47%
2026-03-29	–	–	–	–	94.36%
2026-05-09	–	–	–	–	94.36%