CVE-2022-23302
Published: 18 January 2022
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Priority
Status
Package | Release | Status |
---|---|---|
apache-log4j1.2
Launchpad, Ubuntu, Debian |
bionic |
Released
(1.2.17-8+deb10u1ubuntu0.2)
|
focal |
Released
(1.2.17-9ubuntu0.2)
|
|
impish |
Ignored
(end of life)
|
|
jammy |
Not vulnerable
(1.2.17-11)
|
|
kinetic |
Not vulnerable
(1.2.17-11)
|
|
lunar |
Ignored
(end of life, was needs-triage)
|
|
mantic |
Ignored
(end of life, was needs-triage)
|
|
noble |
Needs triage
|
|
trusty |
Needed
|
|
upstream |
Needs triage
|
|
xenial |
Released
(1.2.17-7ubuntu1+esm1)
Available with Ubuntu Pro |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 8.8 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | Low |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |