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

Posted to issues@activemq.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2021/12/16 12:44:00 UTC

[jira] [Resolved] (AMQ-8431) Log4j old version in use

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

Jean-Baptiste Onofré resolved AMQ-8431.
---------------------------------------
    Fix Version/s:     (was: 5.x)
       Resolution: Invalid

Already planned for ActiveMQ 5.17.x.

> Log4j old version in use
> ------------------------
>
>                 Key: AMQ-8431
>                 URL: https://issues.apache.org/jira/browse/AMQ-8431
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.16.3
>            Reporter: MALOY KUMAR BAIN
>            Priority: Critical
>              Labels: log4jVulnerabilty, production
>
> Hi,
> with the declaration of log4j security vulnerability, I see that the latest verison of ActiveMqconnectionFactory still uses the old log4j packagae. please have this mitigatedd. I am in urgent need of the fixed version of ActiveMq.
> Thanks
> Maloy



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