DEBIAN-CVE-2023-45539

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/CVE-2023-45539
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2023-45539.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2023-45539
Upstream
Published
2023-11-28T20:15:07Z
Modified
2025-09-25T23:28:49.581863Z
Severity
  • 8.2 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N CVSS Calculator
Summary
[none]
Details

HAProxy before 2.8.2 accepts # as part of the URI component, which might allow remote attackers to obtain sensitive information or have unspecified other impact upon misinterpretation of a path_end rule, such as routing index.html#.png to a static server.

References

Affected packages

Debian:11 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.2.9-2+deb11u6

Affected versions

2.*

2.2.9-2
2.2.9-2+deb11u1~bpo10+1
2.2.9-2+deb11u1
2.2.9-2+deb11u2~bpo10+1
2.2.9-2+deb11u2
2.2.9-2+deb11u3~bpo10+1
2.2.9-2+deb11u3
2.2.9-2+deb11u4
2.2.9-2+deb11u5

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.12-1+deb12u1

Affected versions

2.*

2.6.12-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.15-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:14 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2.6.15-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}