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

Posted to notifications@logging.apache.org by "Volkan Yazici (Jira)" <ji...@apache.org> on 2021/12/13 10:24:00 UTC

[jira] [Comment Edited] (LOG4J2-3212) UPgrade

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

Volkan Yazici edited comment on LOG4J2-3212 at 12/13/21, 10:23 AM:
-------------------------------------------------------------------

Please see [the security page|https://logging.apache.org/log4j/2.x/security.html] for details on mitigation techniques regarding the recent CVE-2021-44228. If you still think the provided mitigation techniques fall short of addressing the vulnerability, please elaborate on your reasoning via an email to {{{}private@logging.apache.org{}}}.


was (Author: vy):
Please see [the security page|https://logging.apache.org/log4j/2.x/security.html] for details on mitigation techniques regarding the recent CVE-2021-44228.

> UPgrade
> -------
>
>                 Key: LOG4J2-3212
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3212
>             Project: Log4j 2
>          Issue Type: Bug
>            Reporter: Mayank Jain
>            Priority: Major
>             Fix For: 2.16.0
>
>         Attachments: log4j2-mongodb4-appender-main.zip
>
>




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