A vulnerability was found in HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an "invalid fold." Reference: https://github.com/netty/netty/issues/9866 https://github.com/netty/netty/compare/netty-4.1.43.Final...netty-4.1.44.Final
Created netty tracking bugs for this issue: Affects: fedora-all [bug 1798525]
Mitigation: * Use HTTP/2 instead (clear boundaries between requests) * Disable reuse of backend connections eg. ```http-reuse never``` in HAProxy or whatever equivalent LB settings
This issue has been addressed in the following products: Red Hat AMQ Online 1.3.3 GA Via RHSA-2020:0497 https://access.redhat.com/errata/RHSA-2020:0497
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-2019-20444
External References: https://github.com/elastic/elasticsearch/issues/49396
This issue has been addressed in the following products: AMQ Clients 2.y for RHEL 7 AMQ Clients 2.y for RHEL 8 AMQ Clients 2.y for RHEL 6 Via RHSA-2020:0601 https://access.redhat.com/errata/RHSA-2020:0601
Statement: OpenShift Container Platform ships a vulnerable netty library as part of the logging-elasticsearch5 container. ElasticSearch's security team has stated that the previous vulnerability, CVE-2019-16869, does not pose a substantial practical threat to ElasticSearch 6. We agree that these issues would be difficult to exploit on OpenShift Container Platform so we're reducing the impact of this issue to moderate and may fix it in the future release. Red Hat Satellite ships a vulnerable version of netty embedded in Candlepin. However, the flaw can not be triggered in that context, because HTTP requests are handled by Tomcat, not by netty. A future release may fix this.
This issue has been addressed in the following products: Red Hat Openshift Application Runtimes Via RHSA-2020:0567 https://access.redhat.com/errata/RHSA-2020:0567
Marking AMQ-6 as low as it only uses netty in the context of integration tests, activemq components do not directly rely upon netty.
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2020:0811 https://access.redhat.com/errata/RHSA-2020:0811
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8 Via RHSA-2020:0806 https://access.redhat.com/errata/RHSA-2020:0806
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6 Via RHSA-2020:0804 https://access.redhat.com/errata/RHSA-2020:0804
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7 Via RHSA-2020:0805 https://access.redhat.com/errata/RHSA-2020:0805
This issue has been addressed in the following products: Red Hat AMQ Via RHSA-2020:0922 https://access.redhat.com/errata/RHSA-2020:0922
This issue has been addressed in the following products: Red Hat JBoss AMQ Via RHSA-2020:0939 https://access.redhat.com/errata/RHSA-2020:0939
This issue has been addressed in the following products: Red Hat Single Sign-On Via RHSA-2020:0951 https://access.redhat.com/errata/RHSA-2020:0951
This issue has been addressed in the following products: Red Hat AMQ 7.4.3 Via RHSA-2020:1445 https://access.redhat.com/errata/RHSA-2020:1445
This issue has been addressed in the following products: Red Hat Data Grid 7.3.6 Via RHSA-2020:2321 https://access.redhat.com/errata/RHSA-2020:2321
This issue has been addressed in the following products: EAP-CD 19 Tech Preview Via RHSA-2020:2333 https://access.redhat.com/errata/RHSA-2020:2333
This issue has been addressed in the following products: Red Hat Fuse 7.7.0 Via RHSA-2020:3192 https://access.redhat.com/errata/RHSA-2020:3192
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
Marking Red Hat Jboss Fuse 6 as having a moderate impact, Fuse 6 distributes affected versions of Netty, however its use in Fuse 6 fabric-gateway is not susceptible to the vulnerability as the fabric-gateway will create a new http client upon each gateway invocation, this means there is no multiplexing of connections, this is a prerequisite of HTTP smuggling/desynchronisation attacks. This vulnerability is out of security support scope for the following products: * Red Hat JBoss Fuse 6 Please refer to https://access.redhat.com/support/policy/updates/jboss_notes for more details.
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.