[
https://issues.apache.org/jira/browse/AMQ-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490771#comment-17490771
]
Robbie Gemmell edited comment on AMQ-8482 at 2/11/22, 9:25 AM:
---------------------------------------------------------------
Effective duplicate of _several_ other JIRAs. Please look before raising
needless issues.
AMQ-8472 has switched 5.16.x to [reload4j|https://reload4j.qos.ch/] and a
5.16.4 release is currently-under-vote.
See also AMQ-7426 in progress for switching the later 5.17.x series to Log4J 2.
was (Author: gemmellr):
Effective duplicate of _several_ other JIRAs. Please look before raising
needless issues.
AMQ-8472 has switched 5.16.x to [reload4j|[https://reload4j.qos.ch/],] and a
5.16.4 release is currently-under-vote.
See also AMQ-7426 in progress for switching the later 5.17.x series to Log4J 2.
> JMSAppender Remote Code Execution (CVE-2021-4104)
> --------------------------------------------------
>
> Key: AMQ-8482
> URL: https://issues.apache.org/jira/browse/AMQ-8482
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.16.3
> Reporter: Beng Sokhom
> Priority: Critical
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Dear Support,
> Please help to check in the apache-activemq-5.16.3 is it still remains the
> log4j issue on Apache Log4j-1.2.17 JMSAppender Remote Code Execution
> (CVE-2021-4104).
> path: \apache-activemq-5.16.3\lib\optional\log4j-1.2.17.jar
> Do you have the solution to fixe this issue?
> Thank you.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
