[
https://issues.apache.org/jira/browse/LOG4J2-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459271#comment-17459271
]
Gary D. Gregory commented on LOG4J2-3201:
-----------------------------------------
The class {{ParameterizedNoReferenceMessageFactory$StatusMessage}} was added in
version 2.6. Do you have some other log4j jars on your classpath? You should
make sure the 2.16 jars are on the same place on the classpath as your old
log4j jars.
> Limit the protocols jNDI can use and restrict LDAP.
> ---------------------------------------------------
>
> Key: LOG4J2-3201
> URL: https://issues.apache.org/jira/browse/LOG4J2-3201
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Reporter: Ralph Goers
> Priority: Major
> Fix For: 2.15.0
>
>
> LDAP needs to be limited in the servers and classes it can access. JNDI
> should only support the java, ldap, and ldaps protocols by default.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
