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

Posted to dev@atlas.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/12/11 23:00:00 UTC

[jira] [Commented] (ATLAS-4505) Update log4j2 version to 2.15.0

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

ASF subversion and git services commented on ATLAS-4505:
--------------------------------------------------------

Commit 9383be7e94d64d514372b270a1c2e79d27dc5a75 in atlas's branch refs/heads/master from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9383be7 ]

Merge pull request #153 from deadwind4/ATLAS-4505

ATLAS-4505: Update log4j2 version to 2.15.0

> Update log4j2 version to 2.15.0
> -------------------------------
>
>                 Key: ATLAS-4505
>                 URL: https://issues.apache.org/jira/browse/ATLAS-4505
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 2.2.0
>            Reporter: Ada Wong
>            Priority: Blocker
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 2.0 <= Apache log4j2 <= 2.14.1 have a RCE zero day.
> [https://logging.apache.org/log4j/2.x/security.html]
> 2.15.0 is released to maven central - [https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/2.15.0/]
>  
> [https://www.cyberkendra.com/2021/12/worst-log4j-rce-zeroday-dropped-on.html]
> [https://www.lunasec.io/docs/blog/log4j-zero-day/]



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