You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Jason-Morries Adam (Jira)" <ji...@apache.org> on 2022/01/13 08:53:00 UTC

[jira] [Commented] (KNOX-2697) Upgrade Log4j2 to 2.16

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

Jason-Morries Adam commented on KNOX-2697:
------------------------------------------

Hi,

can you upgrade to 2.17.1 directly because of the new findings in Log4J 2.16?

> Upgrade Log4j2 to 2.16
> ----------------------
>
>                 Key: KNOX-2697
>                 URL: https://issues.apache.org/jira/browse/KNOX-2697
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 1.6.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> See details here: [https://lists.apache.org/thread/d6v4r6nosxysyq9rvnr779336yf0woz4]
> Reason for the release: [https://nvd.nist.gov/vuln/detail/CVE-2021-44228]



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