GitHub Advisory DatabaseGHSA-JFH8-C2JP-5V3QRemote code injection in Log4j
10 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
9.3 High
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
0.976 High
EPSS
Percentile
100.0%
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: 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.
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. More information is available on the GitHub Security Advisory for CVE-2021-45046.
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.
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.
References
packetstormsecurity.com/files/165225/Apache-Log4j2-2.14.1-Remote-Code-Execution.html
packetstormsecurity.com/files/165260/VMware-Security-Advisory-2021-0028.html
packetstormsecurity.com/files/165261/Apache-Log4j2-2.14.1-Information-Disclosure.html
packetstormsecurity.com/files/165270/Apache-Log4j2-2.14.1-Remote-Code-Execution.html
packetstormsecurity.com/files/165281/Log4j2-Log4Shell-Regexes.html
packetstormsecurity.com/files/165282/Log4j-Payload-Generator.html
packetstormsecurity.com/files/165306/L4sh-Log4j-Remote-Code-Execution.html
packetstormsecurity.com/files/165307/Log4j-Remote-Code-Execution-Word-Bypassing.html
packetstormsecurity.com/files/165311/log4j-scan-Extensive-Scanner.html
packetstormsecurity.com/files/165371/VMware-Security-Advisory-2021-0028.4.html
packetstormsecurity.com/files/165532/Log4Shell-HTTP-Header-Injection.html
packetstormsecurity.com/files/165642/VMware-vCenter-Server-Unauthenticated-Log4Shell-JNDI-Injection-Remote-Code-Execution.html
packetstormsecurity.com/files/165673/UniFi-Network-Application-Unauthenticated-Log4Shell-Remote-Code-Execution.html
packetstormsecurity.com/files/167794/Open-Xchange-App-Suite-7.10.x-Cross-Site-Scripting-Command-Injection.html
packetstormsecurity.com/files/167917/MobileIron-Log4Shell-Remote-Command-Execution.html
packetstormsecurity.com/files/171626/AD-Manager-Plus-7122-Remote-Code-Execution.html
seclists.org/fulldisclosure/2022/Dec/2
seclists.org/fulldisclosure/2022/Jul/11
seclists.org/fulldisclosure/2022/Mar/23
www.openwall.com/lists/oss-security/2021/12/10/1
www.openwall.com/lists/oss-security/2021/12/10/2
www.openwall.com/lists/oss-security/2021/12/10/3
www.openwall.com/lists/oss-security/2021/12/13/1
www.openwall.com/lists/oss-security/2021/12/13/2
www.openwall.com/lists/oss-security/2021/12/14/4
www.openwall.com/lists/oss-security/2021/12/15/3
cert-portal.siemens.com/productcert/pdf/ssa-397453.pdf
cert-portal.siemens.com/productcert/pdf/ssa-479842.pdf
cert-portal.siemens.com/productcert/pdf/ssa-661247.pdf
cert-portal.siemens.com/productcert/pdf/ssa-714170.pdf
github.com/advisories/GHSA-7rjr-3q55-vv33
github.com/advisories/GHSA-jfh8-c2jp-5v3q
github.com/apache/logging-log4j2/pull/608
github.com/cisagov/log4j-affected-db
github.com/cisagov/log4j-affected-db/blob/develop/SOFTWARE-LIST.md
github.com/nu11secur1ty/CVE-mitre/tree/main/CVE-2021-44228
github.com/tangxiaofeng7/apache-log4j-poc
issues.apache.org/jira/browse/LOG4J2-3198
issues.apache.org/jira/browse/LOG4J2-3201
issues.apache.org/jira/browse/LOG4J2-3214
issues.apache.org/jira/browse/LOG4J2-3221
lists.debian.org/debian-lts-announce/2021/12/msg00007.html
lists.fedoraproject.org/archives/list/[email protected]/message/M5CSVUNV4HWZZXGOKNSK6L7RPM7BOKIB/
lists.fedoraproject.org/archives/list/[email protected]/message/VU57UJDCFIASIO35GC55JMKSRXJMCDFM/
logging.apache.org/log4j/2.x/changes-report.html#a2.15.0
logging.apache.org/log4j/2.x/manual/lookups.html#JndiLookup
logging.apache.org/log4j/2.x/manual/migration.html
logging.apache.org/log4j/2.x/security.html
msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2/
nvd.nist.gov/vuln/detail/CVE-2021-44228
psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032
security.netapp.com/advisory/ntap-20211210-0007/
support.apple.com/kb/HT213189
tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd
twitter.com/kurtseifried/status/1469345530182455296
www.bentley.com/en/common-vulnerability-exposure/be-2022-0001
www.debian.org/security/2021/dsa-5020
www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00646.html
www.kb.cert.org/vuls/id/930724
www.nu11secur1ty.com/2021/12/cve-2021-44228.html
www.oracle.com/security-alerts/alert-cve-2021-44228.html
www.oracle.com/security-alerts/cpuapr2022.html
www.oracle.com/security-alerts/cpujan2022.html
Related
10 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
9.3 High
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:M/Au:N/C:C/I:C/A:C
0.976 High
EPSS
Percentile
100.0%