# CVE-2024-52528: Auth Token can be passed dummy or wrong the middleware response is 200 OK

> Attackers can bypass authentication restrictions in Budget Control Gateway by passing dummy or invalid auth tokens, gaining unauthorized access.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-jqx6-gm7f-vp7m

## What is CVE-2024-52528?

CVE-2024-52528 is a critical authentication bypass vulnerability in BudgetControl Gateway, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Budget Control Gateway acts as an entry point for incoming requests and routes them to the appropriate microservices for Budget Control. Budget Control Gateway does not properly validate auth tokens, which allows attackers to bypass intended restrictions. This vulnerability is fixed in 1.5.2.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2024-52528 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52528 is a critical authentication bypass vulnerability in BudgetControl Gateway, published on 15 Nov 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-52528 in the wild and no public exploit code.

Affected product: BudgetControl Gateway. 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-52528/ (Markdown: https://insights.sbomify.com/CVE-2024-52528/index.md)
```

## Sources

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

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