You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2022/01/17 20:09:00 UTC
[jira] [Resolved] (LOG4J2-3224) Log4j 2.13.0
[ https://issues.apache.org/jira/browse/LOG4J2-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker resolved LOG4J2-3224.
---------------------------------
Resolution: Information Provided
> 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)