CVE-2021-44228: Log4j core Remote Code Injection Vulnerability
CRITICAL
Advisory Identifier:
GHSA-jfh8-c2jp-5v3q
Advisory Summary
CVE-2021-44228 is a CRITICAL (CVSS 10.0) remote code injection vulnerability (CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')) affecting Log4j core libraries in the Maven ecosystem. The issue involves remote code injection in log4j. Remediation is available by upgrading affected packages to version 2.15.0, 2.3.1, 2.12.2, 1.9.2, 1.10.8, 1.11.10, 2.0.11.
CVE-2021-44228 at a Glance
CVE Identifier
CVE-2021-44228
GHSA Identifier
GHSA-jfh8-c2jp-5v3q
Severity
CRITICAL
CVSS v3.1 Base Score
10.0
CWE Classification
CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')
Affected Product
Log4j core
Package Ecosystem
Maven
Published Date
Last Updated
Security Impact
CVSS: 10.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:H).
Attack Vector
Network (AV:N)
Attack Complexity
Low (AC:L)
Privileges Required
None (PR:N)
User Interaction
None (UI:N)
Scope
Changed (S:C)
Confidentiality
High (C:H)
Integrity
High (I:H)
Availability
High (A:H)
How to Fix CVE-2021-44228
To remediate this vulnerability, upgrade all affected Log4j core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
org.apache.logging.log4j:log4j-core
fixed: 2.15.0
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.15.0</version>
</dependency>
org.apache.logging.log4j:log4j-core
fixed: 2.3.1
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.3.1</version>
</dependency>
org.apache.logging.log4j:log4j-core
fixed: 2.12.2
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.12.2</version>
</dependency>
com.guicedee.services:log4j-core
fixed: Latest secure release
<dependency>
<groupId>com.guicedee.services</groupId>
<artifactId>log4j-core</artifactId>
<version>Latest secure release</version>
</dependency>
org.xbib.elasticsearch:log4j
fixed: Latest secure release
<dependency>
<groupId>org.xbib.elasticsearch</groupId>
<artifactId>log4j</artifactId>
<version>Latest secure release</version>
</dependency>
uk.co.nichesolutions.logging.log4j:log4j-core
fixed: Latest secure release
<dependency>
<groupId>uk.co.nichesolutions.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>Latest secure release</version>
</dependency>
org.ops4j.pax.logging:pax-logging-log4j2
fixed: 1.9.2
<dependency>
<groupId>org.ops4j.pax.logging</groupId>
<artifactId>pax-logging-log4j2</artifactId>
<version>1.9.2</version>
</dependency>
org.ops4j.pax.logging:pax-logging-log4j2
fixed: 1.10.8
<dependency>
<groupId>org.ops4j.pax.logging</groupId>
<artifactId>pax-logging-log4j2</artifactId>
<version>1.10.8</version>
</dependency>
org.ops4j.pax.logging:pax-logging-log4j2
fixed: 1.11.10
<dependency>
<groupId>org.ops4j.pax.logging</groupId>
<artifactId>pax-logging-log4j2</artifactId>
<version>1.11.10</version>
</dependency>
org.ops4j.pax.logging:pax-logging-log4j2
fixed: 2.0.11
<dependency>
<groupId>org.ops4j.pax.logging</groupId>
<artifactId>pax-logging-log4j2</artifactId>
<version>2.0.11</version>
</dependency>
Verify Direct and Transitive Dependencies
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.apache.logging.log4jHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2021-44228, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.apache.logging.log4jAnalyze the terminal output to locate any version of Log4j core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.15.0), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.apache.logging.log4j command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection'), where the product constructs all or part of an expression language (el) statement in a framework such as a java server page (jsp) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended el statement before it is executed. In Log4j core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
# Summary
Log4j versions prior to 2.16.0 are subject to a remote code execution vulnerability via the ldap JNDI parser.
As per [Apache's Log4j security guide](https://logging.apache.org/log4j/2.x/security.html): Apache Log4j2 <=2.14.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.16.0, this behavior has been disabled by default.
Log4j version 2.15.0 contained an earlier fix for the vulnerability, but that patch did not disable attacker-controlled JNDI lookups in all situations. For more information, see the `Updated advice for version 2.16.0` section of this advisory.
# Impact
Logging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.
# Affected versions
Any Log4J version prior to v2.15.0 is affected to this specific issue.
The v1 branch of Log4J which is considered End Of Life (EOL) is vulnerable to other RCE vectors so the recommendation is to still update to 2.16.0 where possible.
## Security releases
Additional backports of this fix have been made available in versions 2.3.1, 2.12.2, and 2.12.3
## Affected packages
Only the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.
# Remediation Advice
## Updated advice for version 2.16.0
The Apache Logging Services team provided updated mitigation advice upon the release of version 2.16.0, which [disables JNDI by default and completely removes support for message lookups](https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0).
Even in version 2.15.0, lookups used in layouts to provide specific pieces of context information will still recursively resolve, possibly triggering JNDI lookups. This problem is being tracked as [CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046). More information is available on the [GitHub Security Advisory for CVE-2021-45046](https://github.com/advisories/GHSA-7rjr-3q55-vv33).
Users who want to avoid attacker-controlled JNDI lookups but cannot upgrade to 2.16.0 must [ensure that no such lookups resolve to attacker-provided data and ensure that the the JndiLookup class is not loaded](https://issues.apache.org/jira/browse/LOG4J2-3221).
Please note that Log4J v1 is End Of Life (EOL) and will not receive patches for this issue. Log4J v1 is also vulnerable to other RCE vectors and we recommend you migrate to Log4J 2.16.0 where possible.
CVE-2021-44228 Affected Log4j core Versions
10 component(s)
Fixed Versions:
2.15.02.3.12.12.21.9.21.10.81.11.102.0.11
| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.apache.logging.log4j:log4j-core
|
Maven |
≥ 2.13.0
< 2.15.0
|
2.15.0
|
|
org.apache.logging.log4j:log4j-core
|
Maven |
≥ 2.0-beta9
< 2.3.1
|
2.3.1
|
|
org.apache.logging.log4j:log4j-core
|
Maven |
≥ 2.4
< 2.12.2
|
2.12.2
|
|
com.guicedee.services:log4j-core
|
Maven |
≤ 1.2.1.2-jre17
|
|
|
org.xbib.elasticsearch:log4j
|
Maven |
6.3.2.1
All 1 versions
6.3.2.1
|
None specified
|
|
uk.co.nichesolutions.logging.log4j:log4j-core
|
Maven |
2.6.3-CUSTOM
All 1 versions
2.6.3-CUSTOM
|
None specified
|
|
org.ops4j.pax.logging:pax-logging-log4j2
|
Maven |
≥ 1.8.0
< 1.9.2
|
1.9.2
|
|
org.ops4j.pax.logging:pax-logging-log4j2
|
Maven |
≥ 1.10.0
< 1.10.8
|
1.10.8
|
|
org.ops4j.pax.logging:pax-logging-log4j2
|
Maven |
≥ 1.11.0
< 1.11.10
|
1.11.10
|
|
org.ops4j.pax.logging:pax-logging-log4j2
|
Maven |
≥ 2.0.0
< 2.0.11
|
2.0.11
|
References
NVD — CVE-2021-44228
NVD
https://nvd.nist.gov/vuln/detail/CVE-2021-44228
Log4j core Source Repository
REPOSITORY
https://github.com/apache/logging-log4j2/pull/608
Log4j core Source Repository
REPOSITORY
https://github.com/github/advisory-database/pull/5501
cert-portal.siemens.com/productcert/pdf/ssa...
WEB
https://cert-portal.siemens.com/productcert/pdf/ssa-397453.pdf
Log4j core Security Information
SECURITY
https://packetstormsecurity.com/files/165673/UniFi-Network-Application-Unauthenticated-Log4Shell-Remote-Code-Execution.html
Log4j core Security Information
SECURITY
https://packetstormsecurity.com/files/167794/Open-Xchange-App-Suite-7.10.x-Cross-Site-Scripting-Command-Injection.html
Log4j core Security Information
SECURITY
https://packetstormsecurity.com/files/167917/MobileIron-Log4Shell-Remote-Command-Execution.html
Log4j core Security Information
SECURITY
https://packetstormsecurity.com/files/171626/AD-Manager-Plus-7122-Remote-Code-Execution.html
psirt.global.sonicwall.com/vuln-detail/snwlid-...
WEB
https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032
Log4j core Security Information
SECURITY
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd
seclists.org/fulldisclosure/2022...
WEB
https://seclists.org/fulldisclosure/2022/Dec/2
seclists.org/fulldisclosure/2022...
WEB
https://seclists.org/fulldisclosure/2022/Jul/11
seclists.org/fulldisclosure/2022...
WEB
https://seclists.org/fulldisclosure/2022/Mar/23
Log4j core Security Information
SECURITY
https://security.netapp.com/advisory/ntap-20211210-0007
support.apple.com/kb/ht213189
WEB
https://support.apple.com/kb/HT213189
Log4j core Security Information
SECURITY
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd
twitter.com/kurtseifried/status...
WEB
https://twitter.com/kurtseifried/status/1469345530182455296
www.bentley.com/en/common-vulnerabi...
WEB
https://www.bentley.com/en/common-vulnerability-exposure/be-2022-0001
www.cisa.gov/known-exploited-vul...
WEB
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-44228
Log4j core Security Information
SECURITY
https://www.debian.org/security/2021/dsa-5020
Log4j core Security Information
SECURITY
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00646.html
www.kb.cert.org/vuls/id/930724
WEB
https://www.kb.cert.org/vuls/id/930724
www.nu11secur1ty.com/2021/12/cve-2021-44...
WEB
https://www.nu11secur1ty.com/2021/12/cve-2021-44228.html
Log4j core Security Information
SECURITY
https://www.oracle.com/security-alerts/alert-cve-2021-44228.html
Log4j core Security Information
SECURITY
https://www.oracle.com/security-alerts/cpuapr2022.html
Log4j core Security Information
SECURITY
https://www.oracle.com/security-alerts/cpujan2022.html
cert-portal.siemens.com/productcert/pdf/ssa...
WEB
https://cert-portal.siemens.com/productcert/pdf/ssa-479842.pdf
cert-portal.siemens.com/productcert/pdf/ssa...
WEB
https://cert-portal.siemens.com/productcert/pdf/ssa-661247.pdf
cert-portal.siemens.com/productcert/pdf/ssa...
WEB
https://cert-portal.siemens.com/productcert/pdf/ssa-714170.pdf
GitHub Advisory / Wiki
ADVISORY
https://github.com/advisories/GHSA-7rjr-3q55-vv33
Log4j core Source Repository
REPOSITORY
https://github.com/apache/logging-log4j2
Log4j core Source Repository
REPOSITORY
https://github.com/cisagov/log4j-affected-db
Log4j core Source Repository
REPOSITORY
https://github.com/cisagov/log4j-affected-db/blob/develop/SOFTWARE-LIST.md
Log4j core Source Repository
REPOSITORY
https://github.com/nu11secur1ty/CVE-mitre/tree/main/CVE-2021-44228
Log4j core Source Repository
REPOSITORY
https://github.com/tangxiaofeng7/apache-log4j-poc
issues.apache.org/jira/browse/log4j2-...
WEB
https://issues.apache.org/jira/browse/LOG4J2-3198
issues.apache.org/jira/browse/log4j2-...
WEB
https://issues.apache.org/jira/browse/LOG4J2-3201
issues.apache.org/jira/browse/log4j2-...
WEB
https://issues.apache.org/jira/browse/LOG4J2-3214
issues.apache.org/jira/browse/log4j2-...
WEB
https://issues.apache.org/jira/browse/LOG4J2-3221
lists.debian.org/debian-lts-announce...
WEB
https://lists.debian.org/debian-lts-announce/2021/12/msg00007.html
lists.fedoraproject.org/archives/list/packa...
WEB
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M5CSVUNV4HWZZXGOKNSK6L7RPM7BOKIB
lists.fedoraproject.org/archives/list/packa...
WEB
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VU57UJDCFIASIO35GC55JMKSRXJMCDFM
lists.fedoraproject.org/archives/list/packa...
WEB
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M5CSVUNV4HWZZXGOKNSK6L7RPM7BOKIB
lists.fedoraproject.org/archives/list/packa...
WEB
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VU57UJDCFIASIO35GC55JMKSRXJMCDFM
logging.apache.org/log4j/2.x/changes-r...
WEB
https://logging.apache.org/log4j/2.x/changes-report.html#a2.15.0
logging.apache.org/log4j/2.x/manual/lo...
WEB
https://logging.apache.org/log4j/2.x/manual/lookups.html#JndiLookup
logging.apache.org/log4j/2.x/manual/mi...
WEB
https://logging.apache.org/log4j/2.x/manual/migration.html
Log4j core Security Information
SECURITY
https://logging.apache.org/log4j/2.x/security.html
msrc-blog.microsoft.com/2021/12/11/microsof...
WEB
https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165225/Apache-Log4j2-2.14.1-Remote-Code-Execution.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165260/VMware-Security-Advisory-2021-0028.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165261/Apache-Log4j2-2.14.1-Information-Disclosure.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165270/Apache-Log4j2-2.14.1-Remote-Code-Execution.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165281/Log4j2-Log4Shell-Regexes.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165282/Log4j-Payload-Generator.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165306/L4sh-Log4j-Remote-Code-Execution.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165307/Log4j-Remote-Code-Execution-Word-Bypassing.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165311/log4j-scan-Extensive-Scanner.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165371/VMware-Security-Advisory-2021-0028.4.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165532/Log4Shell-HTTP-Header-Injection.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165642/VMware-vCenter-Server-Unauthenticated-Log4Shell-JNDI-Injection-Remote-Code-Execution.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/165673/UniFi-Network-Application-Unauthenticated-Log4Shell-Remote-Code-Execution.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/167794/Open-Xchange-App-Suite-7.10.x-Cross-Site-Scripting-Command-Injection.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/167917/MobileIron-Log4Shell-Remote-Command-Execution.html
Log4j core Security Information
SECURITY
http://packetstormsecurity.com/files/171626/AD-Manager-Plus-7122-Remote-Code-Execution.html
seclists.org/fulldisclosure/2022...
WEB
http://seclists.org/fulldisclosure/2022/Dec/2
seclists.org/fulldisclosure/2022...
WEB
http://seclists.org/fulldisclosure/2022/Jul/11
seclists.org/fulldisclosure/2022...
WEB
http://seclists.org/fulldisclosure/2022/Mar/23
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/10/1
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/10/2
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/10/3
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/13/1
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/13/2
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/14/4
Log4j core Security Information
SECURITY
http://www.openwall.com/lists/oss-security/2021/12/15/3
Frequently Asked Questions
What is CVE-2021-44228?
CVE-2021-44228 is a security vulnerability in Log4j core involving Remote code injection in Log4j under CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection').
Which Log4j core versions are affected?
Affected versions include releases prior to 2.15.0, 2.3.1, 2.12.2, 1.9.2, 1.10.8, 1.11.10, 2.0.11 across affected packages: org.apache.logging.log4j:log4j-core, com.guicedee.services:log4j-core, org.xbib.elasticsearch:log4j, uk.co.nichesolutions.logging.log4j:log4j-core, org.ops4j.pax.logging:pax-logging-log4j2.
What version fixes CVE-2021-44228?
Upgrading to 2.15.0, 2.3.1, 2.12.2, 1.9.2, 1.10.8, 1.11.10, 2.0.11 (or the latest patched release for your respective branch) resolves the vulnerability.
Is log4j-core affected?
Yes, org.apache.logging.log4j:log4j-core is affected in releases prior to 2.15.0, 2.3.1, 2.12.2, Latest secure release. Upgrade your dependency to 2.15.0, 2.3.1, 2.12.2, Latest secure release or later.
Is log4j affected?
Yes, org.xbib.elasticsearch:log4j is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2021-44228?
CVE-2021-44228 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:H.
What CWE is associated with CVE-2021-44228?
CVE-2021-44228 is classified under CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') (The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.).
How can I check Maven dependencies for CVE-2021-44228?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.apache.logging.log4j'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON
OSV v1.5 Schema
Normalized schema output
{
"schema_version" : "1.4.0",
"id" : "GHSA-jfh8-c2jp-5v3q",
"modified" : "2025-10-22T19:13:24Z",
"published" : "2021-12-10T00:40:56Z",
"aliases" : [ "CVE-2021-44228" ],
"summary" : "Remote code injection in Log4j",
"details" : "# Summary\n\nLog4j versions prior to 2.16.0 are subject to a remote code execution vulnerability via the ldap JNDI parser.\nAs per [Apache's Log4j security guide](https://logging.apache.org/log4j/2.x/security.html): Apache Log4j2 <=2.14.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.16.0, this behavior has been disabled by default.\n\nLog4j version 2.15.0 contained an earlier fix for the vulnerability, but that patch did not disable attacker-controlled JNDI lookups in all situations. For more information, see the `Updated advice for version 2.16.0` section of this advisory.\n\n# Impact\n\nLogging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input. \n\n# Affected versions\n\nAny Log4J version prior to v2.15.0 is affected to this specific issue.\n\nThe v1 branch of Log4J which is considered End Of Life (EOL) is vulnerable to other RCE vectors so the recommendation is to still update to 2.16.0 where possible.\n\n## Security releases\nAdditional backports of this fix have been made available in versions 2.3.1, 2.12.2, and 2.12.3\n\n## Affected packages\nOnly the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logging.log4j:log4j-api` should be kept at the same version as the `org.apache.logging.log4j:log4j-core` package to ensure compatability if in use.\n\n# Remediation Advice\n\n## Updated advice for version 2.16.0\n\nThe Apache Logging Services team provided updated mitigation advice upon the release of version 2.16.0, which [disables JNDI by default and completely removes support for message lookups](https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0).\nEven in version 2.15.0, lookups used in layouts to provide specific pieces of context information will still recursively resolve, possibly triggering JNDI lookups. This problem is being tracked as [CVE-2021-45046](https://nvd.nist.gov/vuln/detail/CVE-2021-45046). More information is available on the [GitHub Security Advisory for CVE-2021-45046](https://github.com/advisories/GHSA-7rjr-3q55-vv33).\n\nUsers who want to avoid attacker-controlled JNDI lookups but cannot upgrade to 2.16.0 must [ensure that no such lookups resolve to attacker-provided data and ensure that the the JndiLookup class is not loaded](https://issues.apache.org/jira/browse/LOG4J2-3221).\n\nPlease note that Log4J v1 is End Of Life (EOL) and will not receive patches for this issue. Log4J v1 is also vulnerable to other RCE vectors and we recommend you migrate to Log4J 2.16.0 where possible.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.logging.log4j:log4j-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.13.0"
}, {
"fixed" : "2.15.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.logging.log4j:log4j-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0-beta9"
}, {
"fixed" : "2.3.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.logging.log4j:log4j-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.4"
}, {
"fixed" : "2.12.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "com.guicedee.services:log4j-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.2.1.2-jre17"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.xbib.elasticsearch:log4j"
},
"versions" : [ "6.3.2.1" ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "uk.co.nichesolutions.logging.log4j:log4j-core"
},
"versions" : [ "2.6.3-CUSTOM" ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.ops4j.pax.logging:pax-logging-log4j2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.8.0"
}, {
"fixed" : "1.9.2"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.ops4j.pax.logging:pax-logging-log4j2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.10.0"
}, {
"fixed" : "1.10.8"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.ops4j.pax.logging:pax-logging-log4j2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.11.0"
}, {
"fixed" : "1.11.10"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.ops4j.pax.logging:pax-logging-log4j2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "2.0.11"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-44228"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/logging-log4j2/pull/608"
}, {
"type" : "WEB",
"url" : "https://github.com/github/advisory-database/pull/5501"
}, {
"type" : "WEB",
"url" : "https://cert-portal.siemens.com/productcert/pdf/ssa-397453.pdf"
}, {
"type" : "WEB",
"url" : "https://packetstormsecurity.com/files/165673/UniFi-Network-Application-Unauthenticated-Log4Shell-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "https://packetstormsecurity.com/files/167794/Open-Xchange-App-Suite-7.10.x-Cross-Site-Scripting-Command-Injection.html"
}, {
"type" : "WEB",
"url" : "https://packetstormsecurity.com/files/167917/MobileIron-Log4Shell-Remote-Command-Execution.html"
}, {
"type" : "WEB",
"url" : "https://packetstormsecurity.com/files/171626/AD-Manager-Plus-7122-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032"
}, {
"type" : "WEB",
"url" : "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd"
}, {
"type" : "WEB",
"url" : "https://seclists.org/fulldisclosure/2022/Dec/2"
}, {
"type" : "WEB",
"url" : "https://seclists.org/fulldisclosure/2022/Jul/11"
}, {
"type" : "WEB",
"url" : "https://seclists.org/fulldisclosure/2022/Mar/23"
}, {
"type" : "WEB",
"url" : "https://security.netapp.com/advisory/ntap-20211210-0007"
}, {
"type" : "WEB",
"url" : "https://support.apple.com/kb/HT213189"
}, {
"type" : "WEB",
"url" : "https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd"
}, {
"type" : "WEB",
"url" : "https://twitter.com/kurtseifried/status/1469345530182455296"
}, {
"type" : "WEB",
"url" : "https://www.bentley.com/en/common-vulnerability-exposure/be-2022-0001"
}, {
"type" : "WEB",
"url" : "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-44228"
}, {
"type" : "WEB",
"url" : "https://www.debian.org/security/2021/dsa-5020"
}, {
"type" : "WEB",
"url" : "https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00646.html"
}, {
"type" : "WEB",
"url" : "https://www.kb.cert.org/vuls/id/930724"
}, {
"type" : "WEB",
"url" : "https://www.nu11secur1ty.com/2021/12/cve-2021-44228.html"
}, {
"type" : "WEB",
"url" : "https://www.oracle.com/security-alerts/alert-cve-2021-44228.html"
}, {
"type" : "WEB",
"url" : "https://www.oracle.com/security-alerts/cpuapr2022.html"
}, {
"type" : "WEB",
"url" : "https://www.oracle.com/security-alerts/cpujan2022.html"
}, {
"type" : "WEB",
"url" : "https://cert-portal.siemens.com/productcert/pdf/ssa-479842.pdf"
}, {
"type" : "WEB",
"url" : "https://cert-portal.siemens.com/productcert/pdf/ssa-661247.pdf"
}, {
"type" : "WEB",
"url" : "https://cert-portal.siemens.com/productcert/pdf/ssa-714170.pdf"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-7rjr-3q55-vv33"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apache/logging-log4j2"
}, {
"type" : "WEB",
"url" : "https://github.com/cisagov/log4j-affected-db"
}, {
"type" : "WEB",
"url" : "https://github.com/cisagov/log4j-affected-db/blob/develop/SOFTWARE-LIST.md"
}, {
"type" : "WEB",
"url" : "https://github.com/nu11secur1ty/CVE-mitre/tree/main/CVE-2021-44228"
}, {
"type" : "WEB",
"url" : "https://github.com/tangxiaofeng7/apache-log4j-poc"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/LOG4J2-3198"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/LOG4J2-3201"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/LOG4J2-3214"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/LOG4J2-3221"
}, {
"type" : "WEB",
"url" : "https://lists.debian.org/debian-lts-announce/2021/12/msg00007.html"
}, {
"type" : "WEB",
"url" : "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M5CSVUNV4HWZZXGOKNSK6L7RPM7BOKIB"
}, {
"type" : "WEB",
"url" : "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VU57UJDCFIASIO35GC55JMKSRXJMCDFM"
}, {
"type" : "WEB",
"url" : "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M5CSVUNV4HWZZXGOKNSK6L7RPM7BOKIB"
}, {
"type" : "WEB",
"url" : "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VU57UJDCFIASIO35GC55JMKSRXJMCDFM"
}, {
"type" : "WEB",
"url" : "https://logging.apache.org/log4j/2.x/changes-report.html#a2.15.0"
}, {
"type" : "WEB",
"url" : "https://logging.apache.org/log4j/2.x/manual/lookups.html#JndiLookup"
}, {
"type" : "WEB",
"url" : "https://logging.apache.org/log4j/2.x/manual/migration.html"
}, {
"type" : "WEB",
"url" : "https://logging.apache.org/log4j/2.x/security.html"
}, {
"type" : "WEB",
"url" : "https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165225/Apache-Log4j2-2.14.1-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165260/VMware-Security-Advisory-2021-0028.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165261/Apache-Log4j2-2.14.1-Information-Disclosure.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165270/Apache-Log4j2-2.14.1-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165281/Log4j2-Log4Shell-Regexes.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165282/Log4j-Payload-Generator.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165306/L4sh-Log4j-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165307/Log4j-Remote-Code-Execution-Word-Bypassing.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165311/log4j-scan-Extensive-Scanner.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165371/VMware-Security-Advisory-2021-0028.4.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165532/Log4Shell-HTTP-Header-Injection.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165642/VMware-vCenter-Server-Unauthenticated-Log4Shell-JNDI-Injection-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/165673/UniFi-Network-Application-Unauthenticated-Log4Shell-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/167794/Open-Xchange-App-Suite-7.10.x-Cross-Site-Scripting-Command-Injection.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/167917/MobileIron-Log4Shell-Remote-Command-Execution.html"
}, {
"type" : "WEB",
"url" : "http://packetstormsecurity.com/files/171626/AD-Manager-Plus-7122-Remote-Code-Execution.html"
}, {
"type" : "WEB",
"url" : "http://seclists.org/fulldisclosure/2022/Dec/2"
}, {
"type" : "WEB",
"url" : "http://seclists.org/fulldisclosure/2022/Jul/11"
}, {
"type" : "WEB",
"url" : "http://seclists.org/fulldisclosure/2022/Mar/23"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/10/1"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/10/2"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/10/3"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/13/1"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/13/2"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/14/4"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2021/12/15/3"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20", "CWE-400", "CWE-502", "CWE-917" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2021-12-10T00:40:41Z",
"nvd_published_at" : "2021-12-10T10:15:00Z"
}
}