Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
Attack Vector Network
Attack Complexity High
Privileges Required None
Scope Unchanged
Confidentiality Impact None
Integrity Impact None
Availability Impact High
User Interaction None
No CVSS v3.0
Access Vector Network
Access Complexity Medium
Authentication None
Confidentiality Impact None
Integrity Impact None
Availability Impact Partial
AV:N/AC:M/Au:N/C:N/I:N/A:P
Vendors | Products |
---|---|
Oracle |
|
Sonicwall |
|
Netapp |
|
Debian |
|
Apache |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
Configuration 4 [-]
|
Configuration 5 [-]
AND |
|
Configuration 6 [-]
AND |
|
Configuration 7 [-]
AND |
|
Configuration 8 [-]
AND |
|
Configuration 9 [-]
AND |
|
Configuration 10 [-]
|
References
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: apache
Published: 2021-12-18T11:55:08
Updated: 2022-07-25T16:41:57
Reserved: 2021-12-16T00:00:00
Link: CVE-2021-45105
JSON object: View
NVD Information
Status : Analyzed
Published: 2021-12-18T12:15:07.433
Modified: 2022-10-06T17:31:39.640
Link: CVE-2021-45105
JSON object: View
Redhat Information
No data.