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

Posted to notifications@jclouds.apache.org by "Andrew Gaul (Jira)" <ji...@apache.org> on 2021/12/11 23:25:00 UTC

[jira] [Commented] (JCLOUDS-1589) Upgrade to Log4j 2.15.0

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

Andrew Gaul commented on JCLOUDS-1589:
--------------------------------------

Fortunately (?!) our log4j version is so old (1.2.17) that it does not include this functionality and thus the security hole.  Some tests use log4j but this is mostly a jclouds-log4j driver issue.

> Upgrade to Log4j 2.15.0
> -----------------------
>
>                 Key: JCLOUDS-1589
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1589
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-drivers
>    Affects Versions: 2.4.0
>            Reporter: Andrew Gaul
>            Priority: Major
>
> 2.15.0 fixes a critical CVE:
>  
> https://logging.apache.org/log4j/2.x/security.html



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