ZeusQA
Start free

Known exploited vulnerability

CVE-2021-44228

criticalCVSS 3.1 10.0In CISA KEVRansomwareEPSS 100%Published · Apache Software Foundation

The short answer

CVE-2021-44228 affects Apache Software Foundation Apache Log4j2 and is rated critical (CVSS 10.0). CISA added it to the Known Exploited Vulnerabilities catalog on 2021-12-10: attackers are using it, so patch it first. Fixed versions are published for log4j-core (2.15.0, 2.3.1, 2.12.2) and pax-logging-log4j2 (1.9.2, 1.10.8, 1.11.10).

What it is

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

Weakness: CWE-20, CWE-400, CWE-502, CWE-917.

Severity

10.0 critical

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploited (CISA KEV)

Yes, since Dec 10, 2021

Federal due date Dec 24, 2021

EPSS, next 30 days

100%

Higher than 100% of scored CVEs

How it can be exploited

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

What CISA says to do

For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

Affected packages and fixed versions

PackageEcosystemFixed inAdvisory
org.apache.logging.log4j:log4j-coreMaven2.15.0, 2.3.1, 2.12.2GHSA-jfh8-c2jp-5v3q
com.guicedee.services:log4j-coreMavenNo fix yetGHSA-jfh8-c2jp-5v3q
org.xbib.elasticsearch:log4jMavenNo fix yetGHSA-jfh8-c2jp-5v3q
uk.co.nichesolutions.logging.log4j:log4j-coreMavenNo fix yetGHSA-jfh8-c2jp-5v3q
org.ops4j.pax.logging:pax-logging-log4j2Maven1.9.2, 1.10.8, 1.11.10, 2.0.11GHSA-jfh8-c2jp-5v3q

Is it in your code? Drop your lockfile into the free vulnerability check, or let vulnerability watch check your repository every day and open the upgrade as a pull request.

Affected products

Apache Log4j2. NVD's record lists the exact affected versions.

References

Questions

Is CVE-2021-44228 being exploited?

Yes. CISA added CVE-2021-44228 to its Known Exploited Vulnerabilities catalog on 2021-12-10, with a federal remediation due date of 2021-12-24. CISA lists it as used in ransomware campaigns.

How do I fix CVE-2021-44228?

Upgrade to a fixed version: org.apache.logging.log4j:log4j-core (Maven) 2.15.0 or 2.3.1 or 2.12.2; org.ops4j.pax.logging:pax-logging-log4j2 (Maven) 1.9.2 or 1.10.8 or 1.11.10 or 2.0.11. CISA's required action: For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

From NVD, CISA KEV, FIRST EPSS and OSV.dev, checked . Status on NVD: Analyzed. The description is NVD's text, quoted as published.

Related

Know the day a CVE lands in your code

Connect a GitHub repository and ZeusQA checks its dependencies daily, briefs each advisory and opens the fix. Three test runs free, no card.

Start freeSee how a run works