| Package | Affected versions | Patched versions |
|---|---|---|
| org.apache.logging.log4j:log4j-core | ≥ 2.0-beta7, < 2.3.2≥ 2.13.0, < 2.17.1≥ 2.4, < 2.12.4 | 2.3.22.17.12.12.4 |
| org.ops4j.pax.logging:pax-logging-log4j2 | ≥ 1.10.0, < 1.10.9≥ 1.11.0, < 1.11.13≥ 1.8.0, < 1.9.2≥ 2.0.0, < 2.0.14 | 1.10.91.11.131.9.22.0.14 |
| log4j | = 2.0≥ 2.0.1, < 2.3.2≥ 2.13.0, < 2.17.1≥ 2.4, < 2.12.4 | 2.3.22.17.12.12.4 |
| cloudcenter | = 4.10.0.16 | |
| communications brm - elastic charging engine | = 12.0.0.5.0< 12.0.0.4.6 | 12.0.0.4.6 |
| communications diameter signaling router | ≥ 8.0.0.0, ≤ 8.5.1.0≥ 8.3.0.0, ≤ 8.5.1.0 | |
| communications interactive session recorder | = 6.3= 6.4 | |
| communications offline mediation controller | = 12.0.0.5.0< 12.0.0.4.4 | 12.0.0.4.4 |
| flexcube private banking | = 12.1.0 | |
| health sciences data management workbench | = 2.5.2.1= 3.0.0.0= 3.1.0.3 | |
| policy automation | ≥ 12.2.0, ≤ 12.2.24 | |
| policy automation for mobile devices | ≥ 12.2.0, ≤ 12.2.24 | |
| primavera gateway | = 21.12.0≥ 17.12.0, ≤ 17.12.11≥ 18.8.0, ≤ 18.8.13≥ 19.12.0, ≤ 19.12.12≥ 20.12.0, ≤ 20.12.7 | |
| primavera p6 enterprise project portfolio management | = 21.12.0.0≥ 19.12.0, ≤ 19.12.18.0≥ 19.12.0.0, ≤ 19.12.18.0≥ 20.12.0.0, ≤ 20.12.12.0 | |
| primavera unifier | = 18.8= 19.12= 20.12= 21.12 | |
| product lifecycle analytics | = 3.6.1 | |
| retail assortment planning | = 16.0.3 | |
| retail fiscal management | = 14.2 | |
| retail order broker | = 18.0= 19.1 | |
| retail xstore point of service | = 17.0.4= 18.0.3= 19.0.2= 20.0.1= 21.0.1 | |
| siebel ui framework | = 21.12≤ 21.12 | |
| weblogic server | = 12.2.1.3.0= 12.2.1.4.0= 14.1.1.0.0 |
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
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.
This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free