# CVE-2022-0711: Denial of service in haproxy > An attacker can cause a denial of service in HAProxy by sending crafted HTTP responses with Set-Cookie2 headers, triggering an infinite loop. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Mar 2022 - **Updated:** 2 Aug 2024 - **Also known as:** ALPINE-CVE-2022-0711, AZL-8899, BIT-haproxy-2022-0711, DEBIAN-CVE-2022-0711, DSA-5102-1, GHSA-x4fc-x944-v9p7, OESA-2022-1578, OESA-2022-2054, RHSA-2022:1153, RHSA-2022:1336, SUSE-SU-2022:2277-1, UBUNTU-CVE-2022-0711, USN-5312-1, openSUSE-SU-2024:11876-1 ## What is CVE-2022-0711? CVE-2022-0711 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 2 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header. This flaw could allow an attacker to send crafted HTTP response packets which lead to an infinite loop, eventually resulting in a denial of service condition. The highest threat from this vulnerability is availability. Weakness: CWE-835 (Loop with Unreachable Exit Condition) ## Which versions are affected by CVE-2022-0711? 1 open source package ship an affected version, including haproxy. It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `haproxy` | Bitnami | From 2.2.0 | 2.2.21, 2.3.18, 2.4.13 | | `haproxy` | Red Hat:openshift:4.7::el7 | All versions | 0:2.0.19-3.el7 | | `haproxy-debuginfo` | Red Hat:openshift:4.7::el7 | All versions | 0:2.0.19-3.el7 | | `haproxy20` | Red Hat:openshift:4.7::el7 | All versions | 0:2.0.19-3.el7 | | `haproxy` | Red Hat:openshift:4.7::el8 | All versions | 0:2.0.19-3.el8 | | `haproxy-debugsource` | Red Hat:openshift:4.7::el8 | All versions | 0:2.0.19-3.el8 | | `haproxy20` | Red Hat:openshift:4.7::el8 | All versions | 0:2.0.19-3.el8 | | `haproxy20-debuginfo` | Red Hat:openshift:4.7::el8 | All versions | 0:2.0.19-3.el8 | | `haproxy` | Red Hat:openshift:4.8::el8 | All versions | 0:2.2.13-3.el8 | | `haproxy-debugsource` | Red Hat:openshift:4.8::el8 | All versions | 0:2.2.13-3.el8 | | `haproxy22` | Red Hat:openshift:4.8::el8 | All versions | 0:2.2.13-3.el8 | | `haproxy22-debuginfo` | Red Hat:openshift:4.8::el8 | All versions | 0:2.2.13-3.el8 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 2.4.8+git0.d1f8d41e0-150400.3.3.13 | | `haproxy` | openSUSE:Leap 15.4 | All versions | 2.4.8+git0.d1f8d41e0-150400.3.3.13 | | `haproxy` | openSUSE:Tumbleweed | All versions | 2.5.4+git0.e55ab4208-1.1 | Products: Debian Debian Linux, Haproxy Haproxy, Redhat Enterprise Linux, Redhat Openshift Container Platform, Redhat Software Collections. ## How do I fix CVE-2022-0711? Upgrade haproxy to a fixed version for your release line: 2.2.21, 2.3.18 or 2.4.13. ## Is CVE-2022-0711 being exploited? There is no known exploitation of CVE-2022-0711 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-0711 and fix it if it is affected. What it is: CVE-2022-0711 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 2 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-0711 in the wild and no public exploit code. Affected packages and fixed versions: - haproxy (Bitnami): affected from 2.2.0; fixed in 2.2.21, 2.3.18, 2.4.13 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-0711/ (Markdown: https://insights.sbomify.com/CVE-2022-0711/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0711 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0711 - OSV: https://osv.dev/vulnerability/CVE-2022-0711 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-0711/ Summaries are generated and may contain mistakes; the official description above is the record.