CVE-2023-0056: An uncontrolled resource consumption vulnerability was discovered in HAProxy which could crash the service.
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.9% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: haproxy (AlmaLinux:9) 2.4.17-3.el9_1.2; haproxy (Debian:11) 2.2.9-2+deb11u4; haproxy (Debian:12) 2.6.8-1.
Low priority for now. Upgrade to haproxy (AlmaLinux:9) 2.4.17-3.el9_1.2; haproxy (Debian:11) 2.2.9-2+deb11u4; haproxy (Debian:12) 2.6.8-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An uncontrolled resource consumption vulnerability was discovered in HAProxy which could crash the service. This issue could allow an authenticated remote attacker to run a specially crafted malicious server in an OpenShift cluster. The biggest impact is to availability.
- Published
- Mar 23, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-400
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| haproxy | haproxy | cpe:2.3:a:haproxy:haproxy |
| redhat | ceph storage | cpe:2.3:a:redhat:ceph_storage |
| redhat | software collections | cpe:2.3:a:redhat:software_collections |
| redhat | openshift container platform | cpe:2.3:a:redhat:openshift_container_platform |
| redhat | openshift container platform for ibm linuxone | cpe:2.3:a:redhat:openshift_container_platform_for_ibm_linuxone |
| redhat | openshift container platform for power | cpe:2.3:a:redhat:openshift_container_platform_for_power |
| redhat | openshift container platform ibm z systems | cpe:2.3:a:redhat:openshift_container_platform_ibm_z_systems |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | extra packages for enterprise linux | cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject extra packages for enterprise linux8.0
- fedoraproject fedora36
- fedoraproject fedora37
- haproxy haproxyall versions
- redhat ceph storage5.0
- redhat openshift container platform4.10
- redhat openshift container platform4.11
- redhat openshift container platform4.12
- redhat openshift container platform for ibm linuxone4.10
- redhat openshift container platform for ibm linuxone4.11
- redhat openshift container platform for ibm linuxone4.12
- redhat openshift container platform for power4.10
- redhat openshift container platform for power4.11
- redhat openshift container platform for power4.12
- redhat openshift container platform ibm z systems4.10
- redhat openshift container platform ibm z systems4.11
- redhat openshift container platform ibm z systems4.12
- redhat software collectionsall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a haproxy
- unknownaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | haproxy | before 2.4.17-3.el9_1.2 | 2.4.17-3.el9_1.2 |
| Debian:11 | haproxy | before 2.2.9-2+deb11u4 | 2.2.9-2+deb11u4 |
| Debian:12 | haproxy | before 2.6.8-1 | 2.6.8-1 |
| openSUSE:Leap Micro 5.3 | haproxy | before 2.4.8+git0.d1f8d41e0-150400.3.6.1 | 2.4.8+git0.d1f8d41e0-150400.3.6.1 |
| Red Hat:enterprise_linux:9::appstream | haproxy | before 0:2.4.17-3.el9_1.2 | 0:2.4.17-3.el9_1.2 |
| Red Hat:enterprise_linux:9::appstream | haproxy-debuginfo | before 0:2.4.17-3.el9_1.2 | 0:2.4.17-3.el9_1.2 |
| Red Hat:enterprise_linux:9::appstream | haproxy-debugsource | before 0:2.4.17-3.el9_1.2 | 0:2.4.17-3.el9_1.2 |
| Red Hat:openshift_ironic:4.13::el9 | python-werkzeug | before 0:2.0.3-4.el9 | 0:2.0.3-4.el9 |
| Red Hat:openshift_ironic:4.13::el9 | python3-werkzeug | before 0:2.0.3-4.el9 | 0:2.0.3-4.el9 |
| Red Hat:openshift:4.10::el8 | haproxy | before 0:2.2.19-3.el8 | 0:2.2.19-3.el8 |
| Red Hat:openshift:4.10::el8 | haproxy-debugsource | before 0:2.2.19-3.el8 | 0:2.2.19-3.el8 |
| Red Hat:openshift:4.10::el8 | haproxy22 | before 0:2.2.19-3.el8 | 0:2.2.19-3.el8 |
| Red Hat:openshift:4.10::el8 | haproxy22-debuginfo | before 0:2.2.19-3.el8 | 0:2.2.19-3.el8 |
| Red Hat:openshift:4.11::el8 | haproxy | before 0:2.2.24-2.el8 | 0:2.2.24-2.el8 |
| Red Hat:openshift:4.11::el8 | haproxy-debugsource | before 0:2.2.24-2.el8 | 0:2.2.24-2.el8 |
| Red Hat:openshift:4.11::el8 | haproxy22 | before 0:2.2.24-2.el8 | 0:2.2.24-2.el8 |
| Red Hat:openshift:4.11::el8 | haproxy22-debuginfo | before 0:2.2.24-2.el8 | 0:2.2.24-2.el8 |
| Red Hat:openshift:4.12::el8 | buildah | before 1:1.23.4-4.rhaos4.12.el8 | 1:1.23.4-4.rhaos4.12.el8 |
| Red Hat:openshift:4.12::el8 | buildah-debuginfo | before 1:1.23.4-4.rhaos4.12.el8 | 1:1.23.4-4.rhaos4.12.el8 |
| Red Hat:openshift:4.12::el8 | buildah-debugsource | before 1:1.23.4-4.rhaos4.12.el8 | 1:1.23.4-4.rhaos4.12.el8 |
| Red Hat:openshift:4.12::el8 | buildah-tests | before 1:1.23.4-4.rhaos4.12.el8 | 1:1.23.4-4.rhaos4.12.el8 |
| Red Hat:openshift:4.12::el8 | buildah-tests-debuginfo | before 1:1.23.4-4.rhaos4.12.el8 | 1:1.23.4-4.rhaos4.12.el8 |
| Red Hat:openshift:4.12::el8 | conmon | before 2:2.1.2-3.rhaos4.12.el8 | 2:2.1.2-3.rhaos4.12.el8 |
| Red Hat:openshift:4.12::el8 | conmon-debuginfo | before 2:2.1.2-3.rhaos4.12.el8 | 2:2.1.2-3.rhaos4.12.el8 |
+96
Same product
haproxy: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11100In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary bytes53Plan
- CVE-2019-14241HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in prot51Plan
- CVE-2021-40346An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can be exploited to perform an HTTP request smuggling attack, a48Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-0711Mar 2, 2022 · A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header.35Monitor
- ← EarlierCVE-2023-25725Feb 14, 2023 · HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situations, aka "request smu38Monitor
- Later →CVE-2023-0836Mar 29, 2023 · An information leak vulnerability was discovered in HAProxy 2.1, 2.2 before 2.2.27, 2.3, 2.4 before 2.4.21, 2.5 before 2.5.11, 2.6 before 2.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:haproxy | 2.4.17-3.el9_1.2 · AlmaLinux:9 | Package registry (OSV) |
| debian:haproxy | 2.6.8-1 · Debian:12 | Package registry (OSV) |
| opensuse:haproxy | 2.4.8+git0.d1f8d41e0-150400.3.6.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:buildah | 1:1.23.4-4.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:buildah-debuginfo | 1:1.23.4-4.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:buildah-debugsource | 1:1.23.4-4.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:buildah-tests | 1:1.23.4-4.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:buildah-tests-debuginfo | 1:1.23.4-4.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:conmon | 2:2.1.2-3.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:conmon-debuginfo | 2:2.1.2-3.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:conmon-debugsource | 2:2.1.2-3.rhaos4.12.el8 · Red Hat:openshift:4.12::el8 | Package registry (OSV) |
| red hat:haproxy | 0:2.2.24-2.el8 · Red Hat:openshift:4.11::el8 | Package registry (OSV) |
| red hat:haproxy-debugsource | 0:2.2.24-2.el8 · Red Hat:openshift:4.11::el8 | Package registry (OSV) |
| red hat:haproxy22 | 0:2.2.24-2.el8 · Red Hat:openshift:4.11::el8 | Package registry (OSV) |
| red hat:haproxy22-debuginfo | 0:2.2.24-2.el8 · Red Hat:openshift:4.11::el8 | Package registry (OSV) |
| suse:haproxy | 2.0.31-150100.8.31.1 · SUSE:Linux Enterprise High Availability Extension 15 SP1 | Package registry (OSV) |
| suse:haproxy | 2.4.8+git0.d1f8d41e0-150400.3.6.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.