Skip to content
Fencer Intel
critical 9.8

CVE-2019-19330 json

The HTTP/2 implementation in HAProxy before 2.0.10 mishandles headers, as demonstrated by carriage return (CR, ASCII 0xd), line feed (LF, A…

published 6y ago modified 4mo ago also EUVD-2019-8951

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.0%
EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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.

Patch / fix

  • haproxy haproxy 2.0.10
  • haproxy Debian 14, Debian 13, Debian 12 2.0.10-1

debian advisories DEBIAN-CVE-2019-19330

  • haproxy Ubuntu 18.04 LTS 1.8.8-1ubuntu0.9

ubuntu advisories UBUNTU-CVE-2019-19330

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • haproxy openshift 4.4 2.0.13-3.el7
  • haproxy openshift 4.4 2.0.13-3.el8
  • haproxy20 openshift 4.4 2.0.13-3.el7
  • haproxy20 openshift 4.4 2.0.13-3.el8
  • haproxy openshift 3.11 1.8.23-3.el7
  • haproxy18 openshift 3.11 1.8.23-3.el7
  • rh-haproxy18-haproxy RHEL 3 SOFTWARE_COLLECTIONS 1.8.24-2.el7
  • rh-haproxy18-haproxy-syspaths RHEL 3 SOFTWARE_COLLECTIONS 1.8.24-2.el7

red hat advisories RHSA-2020:1936RHSA-2020:1287RHSA-2020:2265RHSA-2020:1725

  • haproxy Alpine 3.8 1.8.23
  • haproxy Alpine 3.9 1.8.23-r0

alpine advisories ALPINE-CVE-2019-19330

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-19330 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-19330 updated cvss 5.9

haproxy: HTTP/2 implementation vulnerable to intermediary encapsulation attacks

  • Red Hat Enterprise Linux AppStream (v. 8) haproxy 1.8.23-3.el8
    fixed: vendor fix RHSA-2020:1725
  • Red Hat OpenShift Container Platform 3.11 haproxy 1.8.23-3.el7, haproxy18 1.8.23-3.el7
    fixed: vendor fix RHSA-2020:1287
  • Red Hat OpenShift Container Platform 4.4 haproxy 2.0.13-3.el7, haproxy 2.0.13-3.el8, haproxy20 2.0.13-3.el7, haproxy20 2.0.13-3.el8
    fixed: vendor fix RHSA-2020:1936
  • Red Hat Software Collections for Red Hat Enterprise Linux Server (v. 7) rh-haproxy18-haproxy 1.8.24-2.el7, rh-haproxy18-haproxy-syspaths 1.8.24-2.el7 Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.6) rh-haproxy18-haproxy 1.8.24-2.el7, rh-haproxy18-haproxy-syspaths 1.8.24-2.el7 Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.7) rh-haproxy18-haproxy 1.8.24-2.el7, rh-haproxy18-haproxy-syspaths 1.8.24-2.el7 Red Hat Software Collections for Red Hat Enterprise Linux Workstation (v. 7) rh-haproxy18-haproxy 1.8.24-2.el7, rh-haproxy18-haproxy-syspaths 1.8.24-2.el7
    fixed: vendor fix RHSA-2020:2265
  • Red Hat Enterprise Linux 6 haproxy Red Hat Enterprise Linux 7 haproxy
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.03% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.