[
https://issues.apache.org/jira/browse/NIFI-9505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464163#comment-17464163
]
Wesley Philip commented on NIFI-9505:
-------------------------------------
It sounds like you're saying NiFi is not affected by
[CVE-2021-45105|https://www.cve.org/CVERecord?id=CVE-2021-45105], but just to
avoid false positives being reported in Security Scans, Log4j is being upgraded
to 2.17.0. Is my understanding correct?
> Upgrade Log4j 2 to 2.17.0
> -------------------------
>
> Key: NIFI-9505
> URL: https://issues.apache.org/jira/browse/NIFI-9505
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Fix For: 1.16.0, 1.15.2
>
>
> Log4j 2 version 2.17.0 addresses a potential vulnerability in non-standard
> logging configurations using Thread Context Map lookup capabilities,
> described in [CVE-2021-45105|https://www.cve.org/CVERecord?id=CVE-2021-45105].
> Although NiFi does not use Log4j 2 for runtime logging, upgrading to version
> 2.17.0 avoids potential references to older versions in external components.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
