You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2021/12/17 01:32:00 UTC

[jira] [Updated] (GROOVY-10410) Bump log4j2 version to 2.16.0 (test dependency)

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

Paul King updated GROOVY-10410:
-------------------------------
    Description: 
Groovy doesn't bundle a version of Log4j in its distribution nor list it as a dependency in its pom (or bom), so isn't directly affected by CVE-2021-44228 (see https://logging.apache.org/log4j/2.x/security.html).

However Groovy users using the {{Log4j2}} AST transform (or using Log4j2 directly) may wish to update there version of Log4j or note the security workarounds mentioned in the above security vulnerability link.

See also: LOG4J2-3201, LOG4J2-3198.

> Bump log4j2 version to 2.16.0 (test dependency)
> -----------------------------------------------
>
>                 Key: GROOVY-10410
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10410
>             Project: Groovy
>          Issue Type: Dependency upgrade
>            Reporter: Paul King
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 3.0.10, 4.0.0-rc-2
>
>
> Groovy doesn't bundle a version of Log4j in its distribution nor list it as a dependency in its pom (or bom), so isn't directly affected by CVE-2021-44228 (see https://logging.apache.org/log4j/2.x/security.html).
> However Groovy users using the {{Log4j2}} AST transform (or using Log4j2 directly) may wish to update there version of Log4j or note the security workarounds mentioned in the above security vulnerability link.
> See also: LOG4J2-3201, LOG4J2-3198.



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