Sensitive-content exposure via fragment-based backend misrouting
Published Nov 28, 2023 · Updated Oct 15, 2024
Improper URI parsing in HAProxy before 2.8.2 allows remote attackers to misroute crafted requests to an unintended backend. The HTTP/1 request-URI parser and path sample fetch treat an unescaped # fragment delimiter as path data, so path_end suffix rules can select the wrong backend. Exposure requires suffix-based routing to a backend that silently trims the fragment; backends that reject the malformed request prevent disclosure.
Summary
What happened
Improper URI parsing in HAProxy before 2.8.2 allows remote attackers to misroute crafted requests to an unintended backend. The HTTP/1 request-URI parser and path sample fetch treat an unescaped # fragment delimiter as path data, so path_end suffix rules can select the wrong backend. Exposure requires suffix-based routing to a backend that silently trims the fragment; backends that reject the malformed request prevent disclosure.
The record
- CVE
- CVE-2023-45539
- Published
- Nov 28, 2023
- Updated
- Oct 15, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-116, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 28, 2023CVE publishedPublication date reported by the CVE source.
- Oct 15, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo