Skip to content
OpenAdvisories
Medium · 6.6 Public exploit CVE-2021-44832 EUVD-2022-0516GHSA-8489-44mv-ggj8

Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

Published Dec 28, 2021 · Updated May 29, 2026 · Assigned by apache

Description

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.

Affected products

VendorProductAffectedFixed
Apache Software Foundation Apache Log4j2 log4j-core – < 2.17.1 2.17.1

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 apache-log4j2 2.17.1-1 —
Debian 13 apache-log4j2 2.17.1-1 —
Debian 12 apache-log4j2 2.17.1-1 —
Debian 9 apache-log4j2 2.12.4-0+deb9u1 DLA-2870-1
ReleasePackageFixed inAdvisory
Ubuntu 26.10 apache-log4j2 No fix yet —
Ubuntu 25.10 apache-log4j2 No fix yet —
Ubuntu 20.04 LTS apache-log4j2 2.17.1-0.20.04.1 USN-5222-1
Ubuntu 18.04 LTS apache-log4j2 2.12.4-0ubuntu0.1 USN-5222-1
Show 1 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro 16.04 LTS apache-log4j2 No fix yet —
ReleasePackageFixed inAdvisory
Red Hat JBoss EAP 7 eap7-log4j 2.17.1-1.redhat_00001.1.el7eap RHSA-2022:1297, RHSA-2022:1296
ReleasePackageFixed inAdvisory
openSUSE Leap 15.3 log4j 2.17.0-4.16.1 openSUSE-SU-2021:4208-1
openSUSE Leap 15.2 log4j 2.17.0-lp152.3.15.1 openSUSE-SU-2022:0002-1

Amazon Linux

ReleasePackageFixed inAdvisory
Amazon Linux 2 aws-kinesis-agent 2.0.6-1.amzn2 ALAS2-2022-1734

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 2 repositories

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

Affected packages

EcosystemPackageAffectedFixedRecord
Maven org.apache.logging.log4j:log4j-core >= 2.0-beta7, < 2.3.2 2.3.2 GHSA-8489-44mv-ggj8
Maven org.apache.logging.log4j:log4j-core >= 2.4, < 2.12.4 2.12.4 GHSA-8489-44mv-ggj8
Maven org.apache.logging.log4j:log4j-core >= 2.13.0, < 2.17.1 2.17.1 GHSA-8489-44mv-ggj8
Maven org.ops4j.pax.logging:pax-logging-log4j2 >= 1.8.0, < 1.9.2 1.9.2 GHSA-8489-44mv-ggj8
Maven org.ops4j.pax.logging:pax-logging-log4j2 >= 1.10.0, < 1.10.9 1.10.9 GHSA-8489-44mv-ggj8
Maven org.ops4j.pax.logging:pax-logging-log4j2 >= 1.11.0, < 1.11.13 1.11.13 GHSA-8489-44mv-ggj8
Maven org.ops4j.pax.logging:pax-logging-log4j2 >= 2.0.0, < 2.0.14 2.0.14 GHSA-8489-44mv-ggj8

Advisories 19

References