Skip to content
Fencer Intel
medium 5.0

CVE-2013-2175 json

HAProxy 1.4 before 1.4.24 and 1.5 before 1.5-dev19, when configured to use hdr_ip or other "hdr_*" functions with a negative occurrence cou…

published 2013-08-19 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-2134

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.6%
EPSS 3.6% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

HAProxy 1.4 before 1.4.24 and 1.5 before 1.5-dev19, when configured to use hdr_ip or other "hdr_*" functions with a negative occurrence count, allows remote attackers to cause a denial of service (negative array index usage and crash) via an HTTP header with a certain number of values, related to the MAX_HDR_HISTORY variable.

Patch / fix

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

debian advisories DEBIAN-CVE-2013-2175

  • haproxy openshift 1.2 1.4.22-6.el6op
  • haproxy RHEL 6 1.4.22-5.el6_4

red hat advisories RHSA-2013:1204RHSA-2013:1120

  • haproxy openSUSE Tumbleweed 1.7.0-1.1

opensuse advisories openSUSE-SU-2024:10114-1

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-2013-2175 updated cvss 5.0

haproxy: http_get_hdr()/get_ip_from_hdr2() MAX_HDR_HISTORY handling denial of service

  • Red Hat Enterprise Linux Load Balancer (v. 6) haproxy 1.4.22-5.el6_4
    fixed: vendor fix RHSA-2013:1120
  • Red Hat OpenShift Enterprise Node haproxy 1.4.22-6.el6op
    fixed: vendor fix RHSA-2013:1204

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

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

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-284 Improper Access Control

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.