CVE-2021-44228 @ Maven-org.apache.logging.log4j:log4j-core-2.11.2

[cxronen]

Vulnerable Package issue exists @ Maven-org.apache.logging.log4j:log4j-core-2.11.2 in branch master

Apache Log4j2 2.0-beta9 through 2.12.1 (excluding 2.3.1) and 2.13.0 through 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.15.0, this behavior has been disabled by default. From version 2.16.0 (for users requiring Java 8 or later), 2.12.2 (for Java 7 users), and 2.3.1 (for Java 6 users) 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.

How to remediate the Log4j RCE vulnerability?

The easiest and most recommended way to remediate this vulnerability is to update to log4j version 2.17.0 or later.

If updating the package is an issue, you may remove the JndiLookup class from the classpath. The command to perform such action is:
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class.

Namespace: cxronen
Repository: BookStore_VSCode
Repository Url: https://github.com/cxronen/BookStore_VSCode
CxAST-Project: cxronen/BookStore_VSCode
CxAST platform scan: 4ac4da5a-0ce1-4c67-8015-eaa5b7b82736
Branch: master
Application: BookStore_VSCode
Severity: HIGH
State: NOT_IGNORED
Status: RECURRENT
CWE: CWE-74

---

Additional Info
Attack vector: NETWORK
Attack complexity: LOW
Confidentiality impact: HIGH
Availability impact: HIGH
Remediation Upgrade Recommendation: 2.12.4

---

References
Advisory
Disclosure
Pull request
Release Note
Issue
Advisory
Commit
Commit
Other
Commit
POC/Exploit
Other