Bug 1798509 (CVE-2019-20445)
Summary: | CVE-2019-20445 netty: HttpObjectDecoder.java allows Content-Length header to accompanied by second Content-Length header | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Dhananjay Arunesh <darunesh> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | unspecified | CC: | aboyko, aileenc, akoufoud, alazarot, almorale, anstephe, aos-bugs, asoldano, atangrin, ataylor, avibelli, bbaranow, bbuckingham, bcourt, bgeorges, bkearney, bmaxwell, bmontgom, brian.stansberry, btotty, cdewolf, chazlett, darran.lofthouse, dkreling, dosoudil, drieden, eparis, etirelli, ganandan, ggaughan, gmalinko, hhudgeon, ibek, iweiss, janstey, java-sig-commits, jawilson, jbalunas, jburrell, jcantril, jerboaa, jochrist, jokerman, jpallich, jperkins, jross, jstastny, jwon, krathod, kverlaen, kwills, lgao, loleary, lthon, lzap, mmccune, mnovotny, msochure, msvehla, mszynkie, nstielau, nwallace, paradhya, pdrozd, pgallagh, pjindal, pmackay, psotirop, rchan, rgodfrey, rguimara, rjerrido, rrajasek, rruss, rsvoboda, rsynek, sdaley, smaestri, sochotni, sokeeffe, spinder, sponnaga, sthorger, swoodman, theute, tom.jenkinson, xiwu |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | netty 4.1.44 | Doc Type: | If docs needed, set a value |
Doc Text: |
A flaw was found in Netty before version 4.1.44, where it accepted multiple Content-Length headers and also accepted both Transfer-Encoding, as well as Content-Length headers where it should reject the message under such circumstances. In circumstances where Netty is used in the context of a server, it could result in a viable HTTP smuggling vulnerability.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-02-13 20:09:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1798511, 1798769, 1798770, 1798771, 1798772, 1798773 | ||
Bug Blocks: | 1798529 |
Description
Dhananjay Arunesh
2020-02-05 14:20:13 UTC
Created netty tracking bugs for this issue: Affects: fedora-all [bug 1798511] 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-20445 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 poses a substantial practical threat to ElasticSearch 6 [1]. We agree that this issue would be difficult to exploit both these vulnerabilities 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. [1] https://github.com/elastic/elasticsearch/issues/49396 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. This issue has been addressed in the following products: Red Hat Fuse 7.9 Via RHSA-2021:3140 https://access.redhat.com/errata/RHSA-2021:3140 |