briantully edited a comment on pull request #680: URL: https://github.com/apache/jmeter/pull/680#issuecomment-993204248
> Any ideas or ETA when would the public release be there with the security fix included? @mazen160 rather than wait for a new release (and potentially new bugs) you can follow the advice given by @FSchumacher and @vlsi above and download the new log4j 2:16.0 release at https://logging.apache.org/log4j/2.x/download.html and replace the JAR files that JMeter uses, which you can find in $JMETER_HOME/libexec/lib/log4j-* There are 4 JAR files to replace: - log4j-1.2-api-2.x.x.jar - log4j-api-2.x.x.jar - log4j-core-2.x.x.jar - log4j-slf4j-impl-2.x.x.jar Just delete the existing log4j-* JAR files in $JMETER_HOME/libexec/lib and then copy over the 4 similarly named files from the 2.16.0 download into $JMETER_HOME/libexec/lib. I did this with my old JMeter 5.2.1 install and it worked like a charm :) @vlsi I know this pull request was merging in version 2.15.0 of log4j, but based on the changelog for log4j, it seems as though the CVE fix is actually in the 2.16.0 release: [https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0)](https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0 [Here is the log4j ticket](https://issues.apache.org/jira/browse/LOG4J2-3208) detailing the fix (disabling JNDI by default) for CVE-2021-44228 that is included in the 2.16.0 release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
