7.5
CWE
125
Advisory Published
CVE Published
Updated

CVE-2018-20615

First published: Mon Dec 31 2018(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.

Credit: cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
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
redhat/haproxy<1.8.17
1.8.17
redhat/haproxy<1.9.1
1.9.1
ubuntu/haproxy<1.8.8-1ubuntu0.3
1.8.8-1ubuntu0.3
ubuntu/haproxy<1.8.13-2ubuntu0.1
1.8.13-2ubuntu0.1
ubuntu/haproxy<1.8.16-2
1.8.16-2
debian/haproxy
2.2.9-2+deb11u6
2.6.12-1+deb12u1
2.9.9-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the vulnerability ID for this issue?

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

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

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

  • 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.

  • 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.

  • 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.

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.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203