This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page.
View CVE-2021-44832 →
DEBIAN-CVE-2021-44832
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) att...
Original description
The description as published by the source.
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Affected packages
Debian:12
apache-log4j2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.1-1"}]}]
Debian:13
apache-log4j2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.1-1"}]}]
Debian:14
apache-log4j2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17.1-1"}]}]
References
- advisory security-tracker.debian.org