# CVE-2024-37082: Auth bypass in haproxy-boshrelease

> Attackers can bypass mTLS authentication in Cloud Foundry deployments using specific HAProxy configurations, allowing unauthorized access to applications.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-w3h5-p6v5-5vjm

## What is CVE-2024-37082?

CVE-2024-37082 is a critical authentication bypass vulnerability in Cloud Foundry haproxy-boshrelease, published on 3 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When deploying Cloud Foundry together with the haproxy-boshrelease and using a non default configuration, it might be possible to craft HTTP requests that bypass mTLS authentication to Cloud Foundry applications. 

You are affected if you have route-services enabled in routing-release and have configured the haproxy-boshrelease property “ha_proxy.forwarded_client_cert” to “forward_only_if_route_service”.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2024-37082?


## How do I fix CVE-2024-37082?

No fix has been published for CVE-2024-37082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-37082 being exploited?

There is no known exploitation of CVE-2024-37082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37082 and fix it if it is affected.

What it is: CVE-2024-37082 is a critical authentication bypass vulnerability in Cloud Foundry haproxy-boshrelease, published on 3 Jul 2024. 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-2024-37082 in the wild and no public exploit code.

Affected product: Cloud Foundry haproxy-boshrelease. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-37082/ (Markdown: https://insights.sbomify.com/CVE-2024-37082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37082
- OSV: https://osv.dev/vulnerability/CVE-2024-37082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-37082/
Summaries are generated and may contain mistakes; the official description above is the record.