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

Posted to dev@atlas.apache.org by "Gustavo Martin (Jira)" <ji...@apache.org> on 2021/12/15 00:59:00 UTC

[jira] [Comment Edited] (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=17459581#comment-17459581 ] 

Gustavo Martin edited comment on ATLAS-4505 at 12/15/21, 12:58 AM:
-------------------------------------------------------------------

Version 2.1.0 is not affected because it is using log4j 1.2.17

Am I right?


was (Author: gumartinm):
Version 2.1.0 is not affected because it is using log4j 1.2.17

> 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
>            Assignee: Ada Wong
>            Priority: Blocker
>             Fix For: 3.0.0, 2.3.0
>
>          Time Spent: 0.5h
>  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)