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

Posted to issues@bigtop.apache.org by "Kengo Seki (Jira)" <ji...@apache.org> on 2022/04/25 15:43:00 UTC

[jira] [Resolved] (BIGTOP-3613) Review log4j configurations for CVE-2021-44228

     [ https://issues.apache.org/jira/browse/BIGTOP-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kengo Seki resolved BIGTOP-3613.
--------------------------------
    Fix Version/s: 3.1.0
         Assignee: Luca Toscano
       Resolution: Fixed

> Review log4j configurations for CVE-2021-44228
> ----------------------------------------------
>
>                 Key: BIGTOP-3613
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3613
>             Project: Bigtop
>          Issue Type: Sub-task
>    Affects Versions: 3.1.0
>            Reporter: Luca Toscano
>            Assignee: Luca Toscano
>            Priority: Major
>             Fix For: 3.1.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Due to CVE-2021-44228, it would be great to avoid shipping 3.1 with the affected log4j versions, or alternatively to apply the workarounds to patch the issue (like -Dlog4j2.formatMsgNoLookups=true etc..)
> More info: https://github.com/advisories/GHSA-jfh8-c2jp-5v3q



--
This message was sent by Atlassian Jira
(v8.20.7#820007)