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

Posted to issues@calcite.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2021/12/14 13:16:00 UTC

[jira] [Resolved] (CALCITE-4939) Upgrade log4j2 version to 2.16.0

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

Stamatis Zampetakis resolved CALCITE-4939.
------------------------------------------
    Resolution: Fixed

Fixed in [f5a652693368ec35388b71f7c8e32ecdebd1558d|https://github.com/apache/calcite/commit/f5a652693368ec35388b71f7c8e32ecdebd1558d]. Thanks for the reviews [~asolimando], [~rubenql], @guiyanakuang!

> Upgrade log4j2 version to 2.16.0
> --------------------------------
>
>                 Key: CALCITE-4939
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4939
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.29.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The [2.16.0 release|https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0] has two additional fixes related to CVE-2021-4422 for hardening security. Calcite uses Log4j2 only for testing purposes so the risk is minimal but it would be good to have them.



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