You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2021/12/21 15:00:03 UTC

[jira] [Commented] (LOG4J2-3268) do we have any work arround for issue LOG4J2-3230 for existing library.

    [ https://issues.apache.org/jira/browse/LOG4J2-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463298#comment-17463298 ] 

Gary D. Gregory commented on LOG4J2-3268:
-----------------------------------------

You MUST update to 2.17.0 to get full mitigation.

 

> do we have any work arround for issue LOG4J2-3230 for existing library.
> -----------------------------------------------------------------------
>
>                 Key: LOG4J2-3268
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3268
>             Project: Log4j 2
>          Issue Type: Bug
>            Reporter: Rajendra Rathore
>            Priority: Minor
>
> do we have any work around for issue LOG4J2-3230 for existing library. I tried setting environment variable LOG4J_FORMAT_MSG_NO_LOOKUPS=true and it working fine, is it valid workaround for old library, can you pls confirm? We are on 2.14.0 version and set the property.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)