Bug 1777584 (CVE-2019-19330)

Summary: CVE-2019-19330 haproxy: HTTP/2 implementation vulnerable to intermediary encapsulation attacks
Product: [Other] Security Response Reporter: Pedro Sampaio <psampaio>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bmontgom, bperkins, carl, eparis, hhorak, jburrell, jeremy, jokerman, jorton, nstielau, pavloos, rohara, sponnaga
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: haproxy 2.0.10, haproxy 1.8.23 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-07 22:31:52 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: 1777585, 1779022, 1779023, 1781027, 1781028, 1781029, 1781030, 1788780    
Bug Blocks: 1777586    

Description Pedro Sampaio 2019-11-27 21:39:24 UTC
The HTTP/2 implementation in HAProxy before 2.0.10 mishandles headers, as demonstrated by carriage return (CR, ASCII 0xd), line feed (LF, ASCII 0xa), and the zero character (NUL, ASCII 0x0), aka Intermediary Encapsulation Attacks.

Upstream patch:

https://git.haproxy.org/?p=haproxy.git;a=commit;h=54f53ef7ce4102be596130b44c768d1818570344
https://git.haproxy.org/?p=haproxy.git;a=commit;h=146f53ae7e97dbfe496d0445c2802dd0a30b0878
https://git.haproxy.org/?p=haproxy-2.0.git;a=commit;h=ac198b92d461515551b95daae20954b3053ce87e

Comment 1 Pedro Sampaio 2019-11-27 21:39:45 UTC
Created haproxy tracking bugs for this issue:

Affects: fedora-all [bug 1777585]

Comment 6 Sam Fowler 2019-12-11 04:25:32 UTC
Statement:

Support for HTTP/2 protocol was added to haproxy in version 1.8, therefore previous versions are not affected by this flaw.

The version of haproxy shipped in OpenShift Container Platform 4 contains the vulnerable code, however exploitation requires setting ROUTER_USE_HTTP2 in the OpenShift Ingress Operator, which is not currently possible. The impact of this vulnerability is therefore reduced in OpenShift Container Platform 4 to Low.

Comment 9 errata-xmlrpc 2020-04-07 19:43:13 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 3.11

Via RHSA-2020:1287 https://access.redhat.com/errata/RHSA-2020:1287

Comment 10 Product Security DevOps Team 2020-04-07 22:31:52 UTC
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-19330

Comment 11 errata-xmlrpc 2020-04-28 15:44:50 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2020:1725 https://access.redhat.com/errata/RHSA-2020:1725

Comment 12 errata-xmlrpc 2020-05-04 10:17:42 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.4

Via RHSA-2020:1936 https://access.redhat.com/errata/RHSA-2020:1936

Comment 13 errata-xmlrpc 2020-05-26 07:35:25 UTC
This issue has been addressed in the following products:

  Red Hat Software Collections for Red Hat Enterprise Linux 7
  Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS
  Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS

Via RHSA-2020:2265 https://access.redhat.com/errata/RHSA-2020:2265