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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | apache-log4j2 | < 2.12.4-0ubuntu0.1 | UNKNOWN |
ubuntu | 20.04 | noarch | apache-log4j2 | < 2.17.1-0.20.04.1 | UNKNOWN |
ubuntu | 21.04 | noarch | apache-log4j2 | < 2.17.1-0.21.04.1 | UNKNOWN |
ubuntu | 21.10 | noarch | apache-log4j2 | < 2.17.1-0.21.10.1 | UNKNOWN |
ubuntu | 23.10 | noarch | apache-log4j2 | < any | UNKNOWN |
ubuntu | 24.04 | noarch | apache-log4j2 | < any | UNKNOWN |
ubuntu | 16.04 | noarch | apache-log4j2 | < any | UNKNOWN |
github.com/apache/logging-log4j2/commit/05db5f9527254632b59aed2a1d78a32c5ab74f16
issues.apache.org/jira/browse/LOG4J2-3293
launchpad.net/bugs/cve/CVE-2021-44832
nvd.nist.gov/vuln/detail/CVE-2021-44832
security-tracker.debian.org/tracker/CVE-2021-44832
ubuntu.com/security/notices/USN-5222-1
www.cve.org/CVERecord?id=CVE-2021-44832