Skip to content
Fencer Vulns
high 7.5

CVE-2024-45506 json

HAProxy 2.9.x before 2.9.10, 3.0.x before 3.0.4, and 3.1.x through 3.1-dev6 allows a remote denial of service for HTTP/2 zero-copy forwardi…

published 2024-09-04 2 y ago modified 2026-09-08 2 mo ago also BIT-haproxy-2024-45506 , EUVD-2024-41515

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

HAProxy 2.9.x before 2.9.10, 3.0.x before 3.0.4, and 3.1.x through 3.1-dev6 allows a remote denial of service for HTTP/2 zero-copy forwarding (h2_send loop) under a certain set of conditions, as exploited in the wild in 2024.

Patch / fix

  • bitnami haproxy 2.9.10, 3.0.4
  • haproxy haproxy 2.9.10, 3.0.4, 3.1-dev6
  • haproxy Debian 14, Debian 13 2.9.10-1

debian advisories DEBIAN-CVE-2024-45506

  • haproxy openSUSE Tumbleweed 3.0.4+git0.7a59afa93-1.1

opensuse advisories openSUSE-SU-2024:14307-1

  • haproxy Azure Linux 3.0 2.9.11-1

azure linux advisories AZL-48668

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

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-2024-45506 updated cvss 7.5

haproxy: potential infinite loop condition in the h2_send() may trigger a DoS

  • Red Hat Ceph Storage 5 haproxy, haproxy22 Red Hat Enterprise Linux 7 haproxy Red Hat Enterprise Linux 8 haproxy Red Hat Enterprise Linux 9 haproxy Red Hat Enterprise Linux 10 haproxy Red Hat OpenShift Container Platform 3.11 haproxy, haproxy18
    +1 more products
    Red Hat OpenShift Container Platform 4 haproxy, haproxy18, haproxy20, haproxy22, haproxy26, haproxy28
    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

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami haproxy
>=2.9.0, <2.9.10
>=3.0.0, <3.0.4
2.9.10
3.0.4

Affected products

  • haproxy haproxy

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

References

Sources

Fencer Vulns 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.