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

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/12/13 21:11:00 UTC

[jira] [Commented] (NIFI-9482) Upgrade Log4j 2 to 2.16.0

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

ASF subversion and git services commented on NIFI-9482:
-------------------------------------------------------

Commit f2314de1c038b97673a1df530eb0000abda870ca in nifi's branch refs/heads/support/nifi-1.15 from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f2314de ]

NIFI-9482 Upgrade Log4j 2 from 2.15.0 to 2.16.0

Signed-off-by: Joe Witt <jo...@apache.org>


> Upgrade Log4j 2 to 2.16.0
> -------------------------
>
>                 Key: NIFI-9482
>                 URL: https://issues.apache.org/jira/browse/NIFI-9482
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.15.1
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>              Labels: security
>             Fix For: 1.16.0, 1.15.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Log4j 2.16.0 incorporates additional security measures, disabling JNDI lookups by default as described in LOG4J-3208.



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