CVE-2023-25725

Advisory lineage Upstream: 0 Downstream: 18
Modified
Published: 14 Feb 2023, 00:00
Last modified:20 Mar 2025, 19:14

Vulnerability Summary

Overall Risk (default)
high
70/100
CVSS Score
9.1 CRITICAL
v3.1 (cve.org)
EPSS Score
17.54% MEDIUM
18% probability -10.45%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

14 Feb 2023, 00:00
Published
Vulnerability first disclosed
20 Mar 2025, 19:14
Last Modified
Vulnerability information updated

Description

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.

CVSS Metrics

  • v3.1•CRITICAL•Score: 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS Trends

Current EPSS score: 17.54%• Percentile: 95%

Techniques & Countermeasures

  • CWE-444•Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

    The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

Affected Systems

  • debian•debian_linux

    10.0 | 11.0

  • haproxy•haproxy

    < 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

References (6)