Closed
Solved
Log4j (I see this running on the Hotfixed nodes) is still vulnerable at version 2.16.
Client reporting question below, is this expected behavior?
-
- Per Robert Clause, 12/20, Seems Log4j (I see this running on the Hotfixed nodes) is still vulnerable at version 2.16.
- NVD - CVE-2021-45105 (nist.gov)
- 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.
- NVD - CVE-2021-45105 (nist.gov)
- Per Robert Clause, 12/20, Seems Log4j (I see this running on the Hotfixed nodes) is still vulnerable at version 2.16.
***Edited by Moderator: Pooja Gadige to add capability tag***
To see attachments, please log in.