CVE-2018-20615: High severity HAProxy HAProxy vulnerability

Published Jan 2, 2019
·
Updated

An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.

Other sources

HAProxy before versions 1.8.17 and 1.9.1 mishandles when a priority flag is set on too short a HEADERS frame in the HTTP/2 decoder, allowing for an out-of-bounds read and subsequent crash. A remote attacker could exploit this to cause a denial of service.

Those who do not use HTTP/2 are unaffected.

— Red Hat

Affected Software

26 affected componentsFixes available
redhat/haproxy<1.8.17
1.8.17
redhat/haproxy<1.9.1
1.9.1
HAProxy HAProxy>=1.8.0<=1.8.19
HAProxy HAProxy=1.9.0
HAProxy HAProxy=1.9.0-dev0
HAProxy HAProxy=1.9.0-dev1
HAProxy HAProxy=1.9.0-dev10
HAProxy HAProxy=1.9.0-dev11
HAProxy HAProxy=1.9.0-dev2
HAProxy HAProxy=1.9.0-dev3
HAProxy HAProxy=1.9.0-dev4
HAProxy HAProxy=1.9.0-dev5
HAProxy HAProxy=1.9.0-dev6
HAProxy HAProxy=1.9.0-dev7
HAProxy HAProxy=1.9.0-dev8
HAProxy HAProxy=1.9.0-dev9
openSUSE Leap=15.0
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
redhat OpenShift Container Platform=3.11
redhat Enterprise Linux=7.0
redhat Enterprise Linux=7.4
redhat Enterprise Linux=7.5
redhat Enterprise Linux=7.6
debian/haproxy
2.2.9-2+deb11u62.2.9-2+deb11u72.6.12-1+deb12u33.0.11-1+deb13u13.0.11-1+deb13u23.2.12-13.2.13-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/haproxy to a version that resolves this vulnerability.

    Fixed in 1.8.17
  2. Upgrade

    Upgrade redhat/haproxy to a version that resolves this vulnerability.

    Fixed in 1.9.1
  3. Upgrade

    Upgrade debian/haproxy to a version that resolves this vulnerability.

    Fixed in 2.2.9-2+deb11u6Fixed in 2.2.9-2+deb11u7Fixed in 2.6.12-1+deb12u3Fixed in 3.0.11-1+deb13u1Fixed in 3.0.11-1+deb13u2Fixed in 3.2.12-1Fixed in 3.2.13-1
  4. Upgrade

    Upgrade HAProxy to a version that resolves this vulnerability.

    Fixed in 1.8.17
  5. Upgrade

    Upgrade HAProxy to a version that resolves this vulnerability.

    Fixed in 1.9.1

Event History

Mar 18, 2019
CVE Published
via MITRE·04:11 PM
Data Sourced
via MITRE·04:11 PM
Description
Mar 21, 2019
Data Sourced
via NVD·04:00 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·04:00 PM
DescriptionSeverity

Frequently Asked Questions

1

What is the vulnerability ID for this issue?

The vulnerability ID for this issue is CVE-2018-20615.

2

What is the severity level of CVE-2018-20615?

The severity level of CVE-2018-20615 is high.

3

Which software versions are affected by CVE-2018-20615?

The affected software versions for CVE-2018-20615 include HAProxy 1.8.x and 1.9.x through 1.9.0.

4

How does CVE-2018-20615 impact the system?

CVE-2018-20615 can result in a crash due to an out-of-bounds read issue in the HTTP/2 protocol decoder.

5

Are there any remedies available for CVE-2018-20615?

Yes, there are remedies available for CVE-2018-20615. Please refer to the references provided for more information.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203