Executed the delete statement ( delete from pegarules.pr_engineclasses where pzclass = ‘JndiLookup.class’ and pzpackage = ‘org/apache/logging/log4j/core/lookup’;
Searched for the files starting with log4j in the application server directory and could see only two jars log4j-core-2.3 &log4j-api-2.3 in the directory (Pega7.31\scripts\lib) so just replace them with the latest jars (log4j-api-2.15.0.jar &log4j-core-2.15.0.jar )
If the system is configured with SMA then need to replace the log4j-api-2.x jar at \Tomcat\webapps\prsysmgmt\WEB-INF\lib.
Since Jar files are replaced with the latest version, Do we need to update any reference/dependency files which are referring to log4j2 jars in the system?
@Eric Rietveld So far, we removed the JNDI class and updated log4j jars to 2.16 . As per CVE-2021-45105, log4j 2.17 is also released. Do we need to update log4j jars to this latest version? Do we need to wait for confirmation from Pega about testing 2.17.0.
@Brahmesh@, there’s no urgency in patching the libs from 2.16 to 2.17. I suggest to wait and monitor our publications as the story unfolds. See also my other posting on this.