You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2020/08/25 02:10:00 UTC

[jira] [Comment Edited] (HADOOP-17221) update log4j-1.2.17 to atlassian version( To Address: CVE-2019-17571)

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

Brahma Reddy Battula edited comment on HADOOP-17221 at 8/25/20, 2:09 AM:
-------------------------------------------------------------------------

[~kihwal] thanks for taking a look.

 

Looks following commit address the issue.

[https://bitbucket.org/atlassian/log4j1/commits/251febb03f8d2b762dbc7977a4893a60d4b006c3]

[https://jira.atlassian.com/browse/CONFSERVER-59549]

Following pull request where it's mentioned.

[https://bitbucket.org/atlassian/log4j1/pull-requests/4/issue-confserver-59549-remove-socket/diff]

  !image-2020-08-25-07-39-09-201.png!

 


was (Author: brahmareddy):
[~kihwal] thanks for taking a look.

 

Looks following commit address the issue.

[https://bitbucket.org/atlassian/log4j1/commits/251febb03f8d2b762dbc7977a4893a60d4b006c3]

[https://jira.atlassian.com/browse/CONFSERVER-59549]

Following pull request where it's mentioned.

[https://bitbucket.org/atlassian/log4j1/pull-requests/4/issue-confserver-59549-remove-socket/diff]

 

!image-2020-08-25-07-35-20-643.png!

> update log4j-1.2.17 to atlassian version( To Address: CVE-2019-17571)
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-17221
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17221
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>            Priority: Major
>         Attachments: HADOOP-17221-001.patch, image-2020-08-25-07-39-09-201.png
>
>
> Currentlly there are no active release under 1.X in log4j and log4j2 is incompatiable to upgrade (see HADOOP-16206 ) for more details.
> But following CVE is reported on log4j 1.2.17..I think,we should consider to update to Atlassian([https://mvnrepository.com/artifact/log4j/log4j/1.2.17-atlassian-0.4]) or redhat versions
> [https://nvd.nist.gov/vuln/detail/CVE-2019-17571]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org