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

Posted to notifications@logging.apache.org by "Edmondo Sena (Jira)" <ji...@apache.org> on 2021/12/14 14:03:00 UTC

[jira] [Comment Edited] (LOG4J2-3224) Log4j 2.13.0

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

Edmondo Sena edited comment on LOG4J2-3224 at 12/14/21, 2:02 PM:
-----------------------------------------------------------------

Thanks Volkan Yazici.

 

In these changes are impacted also the syslog4j_0.9.46.jar and slf4j-log4j12.jar? Are they also impacted? or are they not?


was (Author: JIRAUSER281817):
ThanksVolkan.

 

In these changes is impacted also the syslog4j_0.9.46.jar and slf4j-log4j12.jar? Are they also impacted? or are they not?

> Log4j 2.13.0
> ------------
>
>                 Key: LOG4J2-3224
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3224
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 2.13.0
>            Reporter: Edmondo Sena
>            Priority: Critical
>             Fix For: 2.15.0
>
>
> Given the vulnerabilities of Log4j 2.13.0, does the switch to log4j 2.15.0 have severe design impacts or is it painless? Is version 2.15.0 okay or is version 2.16.0 required?
> Thanks



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