Log4j (I see this running on the Hotfixed nodes) is still vulnerable at version 2.16.

General
, ,
1

Client reporting question below, is this expected behavior?

    1. Per Robert Clause, 12/20, Seems Log4j (I see this running on the Hotfixed nodes) is still vulnerable at version 2.16.
      1. NVD - CVE-2021-45105 (nist.gov)
        1. Details: Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.
2

Hi @kuchj1, yes, the hotfix you installed will bring you to log4j version 2.16. We’ll be shipping 2.17 based patches soon. Please keep monitoring Pegasystems Documentation

3

@Eric Rietveld thank you and happy holidays!