A vulnerability was found in Netty in the way it handles the amount of data it compress and decompress. Compression/Decompression Codecs should enforce memory allocation size limits to avoid OOME or exhaust the memory pool. Reference: https://github.com/netty/netty/pull/9924
The AMQ Broker has been marked as having a low impact, this is because although netty is built and distributed with the AMQ broker its actual use in the product doesn't use the decompression functionality provided by netty (jzlib)
AMQ Online has been marked as having a low impact, this is because although netty distributed with AMQ Online its actual use in the product doesn't use the decompression functionality provided by netty (jzlib)
This issue has been addressed in the following products: Red Hat AMQ Online 1.4.1 GA Via RHSA-2020:1538 https://access.redhat.com/errata/RHSA-2020:1538
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-11612
This issue has been addressed in the following products: Red Hat Openshift Application Runtimes Via RHSA-2020:1422 https://access.redhat.com/errata/RHSA-2020:1422
AMQ Clients has been marked as having a low impact, this is because although netty is built and distributed its actual use in the product doesn't use the decompression functionality provided by netty (jzlib).
This issue has been addressed in the following products: AMQ Clients 2.y for RHEL 6 AMQ Clients 2.y for RHEL 7 AMQ Clients 2.y for RHEL 8 Via RHSA-2020:2605 https://access.redhat.com/errata/RHSA-2020:2605
This issue has been addressed in the following products: Red Hat AMQ Streams 1.5.0 Via RHSA-2020:2618 https://access.redhat.com/errata/RHSA-2020:2618
This issue has been addressed in the following products: Red Hat AMQ Via RHSA-2020:2751 https://access.redhat.com/errata/RHSA-2020:2751
This issue has been addressed in the following products: Red Hat AMQ Via RHSA-2020:3133 https://access.redhat.com/errata/RHSA-2020:3133
This issue has been addressed in the following products: Red Hat Decision Manager Via RHSA-2020:3196 https://access.redhat.com/errata/RHSA-2020:3196
This issue has been addressed in the following products: Red Hat Process Automation Via RHSA-2020:3197 https://access.redhat.com/errata/RHSA-2020:3197
Statement: In OpenShift Container Platform end users don't have direct access to send requests to ElasticSearch. A user could need access to the ElasticSearch service on the internal cluster network in order to be able to send malicious requests to it. Third party scanners flagging Red Hat Satellite due to availability of the higher version packages in Red Hat AMQ Clients (through errata RHSA-2020:2605) compare to the qpid packages from Satellite Tools repository. qpid dependency fixed in errata RHSA-2020:2605 was for Red Hat AMQ Clients and it doesn't necessarily mean that packages from Satellite Tools are affected. These are two different products with different architecture and code-base. Updating the packages from any other repository than the Satellite-tools repository is not recommended for Satellite Customers. Red Hat Satellite 6.7 and earlier ship affected version of netty, however, there is no external connection being exposed and it is used by only Artemis to open an internal connection within the JVM. Since netty does not come into contact with untrusted data, vulnerability is not exposed in product code and there is no breach of Confidentiality, Integrity or Availability expected from this vulnerability. We may update the netty and its dependency in a future release. More information regarding Satellite related packages can be found on KCS: https://access.redhat.com/solutions/5200591
Created netty tracking bugs for this issue: Affects: fedora-all [bug 1865894]
This issue has been addressed in the following products: Red Hat Single Sign-On 7.4.2 Via RHSA-2020:3501 https://access.redhat.com/errata/RHSA-2020:3501
This issue has been addressed in the following products: EAP-CD 20 Tech Preview Via RHSA-2020:3585 https://access.redhat.com/errata/RHSA-2020:3585
This issue has been addressed in the following products: Red Hat Data Grid Via RHSA-2020:3626 https://access.redhat.com/errata/RHSA-2020:3626
This issue has been addressed in the following products: Red Hat Data Grid 7.3.7 Via RHSA-2020:3779 https://access.redhat.com/errata/RHSA-2020:3779
This issue has been addressed in the following products: Red Hat build of Quarkus 1.7.5 Via RHSA-2020:4252 https://access.redhat.com/errata/RHSA-2020:4252
This issue has been addressed in the following products: Red Hat Fuse 7.8.0 Via RHSA-2020:5568 https://access.redhat.com/errata/RHSA-2020:5568
This issue has been addressed in the following products: Red Hat Satellite 6.8 for RHEL 7 Via RHSA-2021:1313 https://access.redhat.com/errata/RHSA-2021:1313
Marking Red Hat Fuse 7 as having a low impact, Fuse 7 distributes affected versions of Netty in the Karaf Narayana transaction manager, however the vulnerable functionality of these artifacts is not used.