# CVE-2023-45539: Information disclosure in n/a > Remote attackers can bypass path_end rules by using hash symbols in URIs, potentially exposing sensitive files or bypassing security controls. - **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Nov 2023 - **Updated:** 15 Oct 2024 - **Also known as:** ALSA-2024:8849, AZL-32061, BIT-haproxy-2023-45539, CLSA-2023-1703008559, CLSA-2023-1703181305, CLSA-2023-1703181677, CLSA-2023-1703183093, CLSA-2023-1703183930, CLSA-2023-1703611617, CLSA-2024-1730920903, CLSA-2026-1776342757, CLSA-2026-1776343034, CLSA-2026-1790671238, DEBIAN-CVE-2023-45539, DLA-3688-1, GHSA-79q7-m98p-qvhp, MINI-6wfm-xrqp-f43j, MINI-g465-fx6g-hr2c, RHSA-2024:10267, RHSA-2024:10271, RHSA-2024:8849, RHSA-2024:8874, RHSA-2024:9945, RLSA-2024:8849, SUSE-SU-2023:4645-1, SUSE-SU-2023:4647-1, SUSE-SU-2024:2377-1, UBUNTU-CVE-2023-45539, USN-6530-1, USN-6530-2 ## What is CVE-2023-45539? CVE-2023-45539 is a high-severity vulnerability in n/a, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-116 (Improper Encoding or Escaping of Output) ## Which versions are affected by CVE-2023-45539? 1 open source package ship an affected version, including haproxy. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `haproxy` | Bitnami | All versions | 2.8.2 | | `haproxy` | AlmaLinux:8 | All versions | 1.8.27-5.el8_10.1 | | `haproxy` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.27-5.el8_10.1 | | `haproxy-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.27-5.el8_10.1 | | `haproxy-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.8.27-5.el8_10.1 | | `haproxy` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.8.23-3.el8_2.1 | | `haproxy-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.8.23-3.el8_2.1 | | `haproxy-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:1.8.23-3.el8_2.1 | | `haproxy` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy-debuginfo` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy-debugsource` | Red Hat:rhel_e4s:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.8.27-5.el8_8.1 | | `haproxy-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.8.27-5.el8_8.1 | | `haproxy-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.8.27-5.el8_8.1 | | `haproxy` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy-debuginfo` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy-debugsource` | Red Hat:rhel_tus:8.4::appstream | All versions | 0:1.8.27-2.el8_4.1 | | `haproxy` | Red Hat:rhel_tus:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy-debuginfo` | Red Hat:rhel_tus:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy-debugsource` | Red Hat:rhel_tus:8.6::appstream | All versions | 0:1.8.27-4.el8_6.1 | | `haproxy` | Rocky Linux:8 | All versions | 0:1.8.27-5.el8_10.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP2 | All versions | 2.0.31-150200.11.26.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP3 | All versions | 2.0.31-150200.11.26.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP4 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | SUSE:Linux Enterprise High Availability Extension 15 SP5 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | openSUSE:Leap 15.4 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | | `haproxy` | openSUSE:Leap 15.5 | All versions | 2.4.22+git0.f8e3218e2-150400.3.19.1 | Products: Haproxy Haproxy. ## How do I fix CVE-2023-45539? Upgrade haproxy to 2.8.2 or later. ## Is CVE-2023-45539 being exploited? There is no known exploitation of CVE-2023-45539 in the wild and no public exploit code. Public exploit code: - HAProxy-CVE-2023-45539-PoC (github_poc): https://github.com/slicingmelon/HAProxy-CVE-2023-45539-PoC ## Other vulnerabilities in n/a - [CVE-2026-55203](https://insights.sbomify.com/CVE-2026-55203/): HAProxy - Integer Overflow in FCGI Demux Record Length Field (critical 9.0) - [CVE-2026-55204](https://insights.sbomify.com/CVE-2026-55204/): HAProxy - NULL Pointer Dereference in hpack_dht_insert Function (high 8.7) - [CVE-2024-45506](https://insights.sbomify.com/CVE-2024-45506/): Denial of service in n/a (high 7.5) - [CVE-2023-0836](https://insights.sbomify.com/CVE-2023-0836/): Information disclosure in HAProxy (high 7.5) - [CVE-2019-18277](https://insights.sbomify.com/CVE-2019-18277/): Other in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-45539 and fix it if it is affected. What it is: CVE-2023-45539 is a high-severity vulnerability in n/a, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-45539 in the wild and no public exploit code. Affected packages and fixed versions: - haproxy (Bitnami): affected all versions; fixed in 2.8.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-45539/ (Markdown: https://insights.sbomify.com/CVE-2023-45539/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45539 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45539 - OSV: https://osv.dev/vulnerability/CVE-2023-45539 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-45539/ Summaries are generated and may contain mistakes; the official description above is the record.