Apache Log4j2 Deserialization of Untrusted Data Vulnerability. Actively exploited: CISA added this vulnerability to its Known Exploited Vulnerabilities catalog on 01/05/2023. Patch affected systems as an emergency. It is known to be used in ransomware campaigns.
| Package | Affected versions | Patched versions |
|---|---|---|
| org.apache.logging.log4j:log4j-core | ≥ 2.13.0, < 2.16.0≥ 2.4.0, < 2.12.2< 2.3.1 | 2.16.02.12.22.3.1 |
| org.ops4j.pax.logging:pax-logging-log4j2 | ≥ 1.10.0, < 1.10.8≥ 1.11.0, < 1.11.11≥ 1.8.0, < 1.9.2≥ 2.0.0, < 2.0.12 | 1.10.81.11.111.9.22.0.12 |
| log4j | = 2.0≥ 2.0.1, < 2.12.2≥ 2.13.0, < 2.16.0 | 2.12.22.16.0 |
| captial | = 2019.1< 2019.1 | 2019.1 |
| desigo cc advanced reports | = 4.0= 4.1= 4.2= 5.0= 5.1 | |
| desigo cc info center | = 5.0= 5.1 | |
| e-car operation center | < 2021-12-13 | 2021-12-13 |
| energy engage | = 3.1 | |
| energyip | = 8.5= 8.6= 8.7= 9.0 | |
| energyip prepay | = 3.7= 3.8 | |
| gma-manager | < 8.6.2j-398 | 8.6.2j-398 |
| industrial edge management hub | < 2021-12-13 | 2021-12-13 |
| mindsphere | < 2021-12-11 | 2021-12-11 |
| navigator | < 2021-12-13 | 2021-12-13 |
| opcenter intelligence | ≤ 3.2 | |
| operation scheduler | ≤ 1.1.3 | |
| sentron powermanager | = 4.1= 4.2 | |
| siguard dsa | = 4.2= 4.3= 4.4 | |
| sipass integrated | = 2.80= 2.85 | |
| siveillance command | ≤ 4.16.2.1 | |
| siveillance identity | = 1.5= 1.6 | |
| solid edge harness design | = 2020< 2020 | 2020 |
| spectrum power 4 | = 4.70< 4.70 | 4.70 |
| spectrum power 7 | = 2.30< 2.30 | 2.30 |
| vesys | = 2019.1< 2019.1 | 2019.1 |
| email security | < 10.0.12 | 10.0.12 |
The fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a remote code execution (RCE) attack.
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.
Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default. This issue can be mitigated in prior releases (< 2.16.0) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class).
Log4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property log4j2.formatMsgNoLookups to true do NOT mitigate this specific vulnerability.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free