This update for log4j fixes the following issue:
This update was imported from SUSE:SLE-15-SP2:Update.
{ "binaries": [ { "disruptor-javadoc": "3.4.4-lp152.2.3.1", "log4j-javadoc": "2.16.0-lp152.3.9.1", "log4j-slf4j": "2.16.0-lp152.3.9.1", "jakarta-servlet": "5.0.0-lp152.2.1", "log4j-jcl": "2.16.0-lp152.3.9.1", "jakarta-servlet-javadoc": "5.0.0-lp152.2.1", "disruptor": "3.4.4-lp152.2.3.1", "log4j": "2.16.0-lp152.3.9.1" } ] }
{ "binaries": [ { "disruptor-javadoc": "3.4.4-lp152.2.3.1", "log4j-javadoc": "2.16.0-lp152.3.9.1", "log4j-slf4j": "2.16.0-lp152.3.9.1", "jakarta-servlet": "5.0.0-lp152.2.1", "log4j-jcl": "2.16.0-lp152.3.9.1", "jakarta-servlet-javadoc": "5.0.0-lp152.2.1", "disruptor": "3.4.4-lp152.2.3.1", "log4j": "2.16.0-lp152.3.9.1" } ] }
{ "binaries": [ { "disruptor-javadoc": "3.4.4-lp152.2.3.1", "log4j-javadoc": "2.16.0-lp152.3.9.1", "log4j-slf4j": "2.16.0-lp152.3.9.1", "jakarta-servlet": "5.0.0-lp152.2.1", "log4j-jcl": "2.16.0-lp152.3.9.1", "jakarta-servlet-javadoc": "5.0.0-lp152.2.1", "disruptor": "3.4.4-lp152.2.3.1", "log4j": "2.16.0-lp152.3.9.1" } ] }