# CVE-2021-44228: Remote code injection in Log4j

Source: https://junglewise.ai/threats/cve-2021-44228-apache-log4j2-remote-code-execution-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2021-12-10. Updated: 2026-05-10  
License: CC BY 4.0 with a link back

CVE-2021-44228 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2021-12-10

Apache Log4j2 JNDI features do not protect against attacker-controlled LDAP and other JNDI-related endpoints. An attacker who can control log messages or parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled.

Technologies: [Apache Log4j2](https://junglewise.ai/threats/technologies/log4j2), [org.apache.logging.log4j:log4j-core (Maven)](https://junglewise.ai/threats/technologies/org-apache-logging-log4j-log4j-core), [org.ops4j.pax.logging:pax-logging-log4j2 (Maven)](https://junglewise.ai/threats/technologies/org-ops4j-pax-logging-pax-logging-log4j2). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache), [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2021-44228 exploited in the wild?** Yes. CVE-2021-44228 is known to be exploited in the wild, first recorded on 10 December 2021. Treat it as urgent.

**How severe is CVE-2021-44228?** Critical severity, with a CVSS score of 3.1, published 10 December 2021.

**Which products and versions are affected?** com.guicedee.services:log4j-core (Maven) ECOSYSTEM:introduced=0,last_affected=1.2.1.2-jre17; org.apache.logging.log4j:log4j-core (Maven) ECOSYSTEM:introduced=2.13.0,fixed=2.15.0; org.ops4j.pax.logging:pax-logging-log4j2 (Maven) ECOSYSTEM:introduced=1.8.0,fixed=1.9.2.

**Is there a fix for CVE-2021-44228?** Yes. org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.15.0 or later; org.ops4j.pax.logging:pax-logging-log4j2 (Maven): upgrade to 1.9.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2021-44228 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2021-44228?** Check whether you run Apache Log4j2, com.guicedee.services:log4j-core (Maven), org.apache.logging.log4j:log4j-core (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.15.0 or later

  ```sh
  # set org.apache.logging.log4j:log4j-core to 2.15.0 in your pom.xml or build.gradle
  ```

- org.ops4j.pax.logging:pax-logging-log4j2 (Maven): upgrade to 1.9.2 or later

  ```sh
  # set org.ops4j.pax.logging:pax-logging-log4j2 to 1.9.2 in your pom.xml or build.gradle
  ```


## Affected products

- Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1)

## Identifiers

- CVE-2021-44228
- GHSA-jfh8-c2jp-5v3q

## Timeline

- 2021-12-10: disclosed
- 2021-12-10: advisory

## Related threats

- [Apache Log4j Core invalid XML output in XmlLayout](https://junglewise.ai/threats/cve-2026-34480-apache-log4j-core-invalid-xml-output-in-xmllayout)
- [Apache Log4j Core log injection in Rfc5424Layout](https://junglewise.ai/threats/cve-2026-34478-apache-log4j-core-log-injection-in-rfc5424layout)
- [Apache Log4j Core improper certificate validation in network appenders](https://junglewise.ai/threats/cve-2026-34477-apache-log4j-core-improper-certificate-validation-in-network)
- [Apache Log4j does not verify the TLS hostname in its Socket Appender](https://junglewise.ai/threats/cve-2025-68161-apache-log4j-does-not-verify-the-tls-hostname-in-its-socket)
- [Apache Log4j 1.x (EOL) allows Denial of Service (DoS)](https://junglewise.ai/threats/cve-2023-26464-apache-log4j-1-x-eol-allows-denial-of-service-dos)