CVE-2021-44832
Published: 28 December 2021
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.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
apache-log4j2 Launchpad, Ubuntu, Debian |
bionic |
Released
(2.12.4-0ubuntu0.1)
|
| focal |
Released
(2.17.1-0.20.04.1)
|
|
| hirsute |
Released
(2.17.1-0.21.04.1)
|
|
| impish |
Released
(2.17.1-0.21.10.1)
|
|
| jammy |
Not vulnerable
(2.17.1-1)
|
|
| kinetic |
Not vulnerable
(2.17.2-1)
|
|
| lunar |
Ignored
(end of life, was needs-triage)
|
|
| mantic |
Needs triage
|
|
| noble |
Needs triage
|
|
| trusty |
Does not exist
|
|
| upstream |
Needs triage
|
|
| xenial |
Needed
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 6.6 |
| Attack vector | Network |
| Attack complexity | High |
| Privileges required | High |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | High |
| Availability impact | High |
| Vector | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H |