ProfessorProfessor@Stuart WeenigThanks.
Although the 2.15 can mitigate, for complete mitigation version 2.16.0 should be used, as this version completely removes the feature. Ideally the class "jndilookup.class" should be removed altogether.
https://logging.apache.org/log4j/2.x/security.html#Fixed_in_Log4j_2.15.0
"It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in a denial of service (DOS) attack. Log4j 2.15.0 restricts JNDI LDAP lookups to localhost by default. Note that previous mitigations involving configuration such as to set the system property log4j2.noFormatMsgLookup to true do NOT mitigate this specific vulnerability."
