CVE-2023-25725: HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situations, aka "request smuggling." The HTTP header parsers in HAProxy may accept...

Critical CVSS 9.1

CVE id
CVE-2023-25725
Published
Last modified

Affected packages

PackageAffected versionsFixed in
HAProxy
Runtimes and servers
< 2.0.31
>= 2.1.0, < 2.2.29
>= 2.3.0, < 2.4.22
>= 2.5.0, < 2.5.12
>= 2.6.0, < 2.6.9
>= 2.7.0, < 2.7.3
2.0.31, 2.2.29, 2.4.22, 2.5.12, 2.6.9, 2.7.3

How to fix it

Upgrade HAProxy to the fixed release of the line you run: 2.0.31, 2.2.29, 2.4.22, 2.5.12, 2.6.9, 2.7.3.

haproxy -v
  • Install the patched HAProxy release of your branch (the haproxy image tag or your packages) and reload it.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situations, aka "request smuggling." The HTTP header parsers in HAProxy may accept empty header field names, which could be used to truncate the list of HTTP headers and thus make some headers disappear after being parsed and processed for HTTP/1.0 and HTTP/1.1. For HTTP/2 and HTTP/3, the impact is limited because the headers disappear before being parsed and processed, as if they had not been sent by the client. The fixed versions are 2.7.3, 2.6.9, 2.5.12, 2.4.22, 2.2.29, and 2.0.31.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.