# CVE-2024-13040: Quanta Computer QOCA aim - Authorization Bypass

> Remote attackers can bypass authorization by manipulating user ID parameters to access other users' features and modify account privileges.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2024
- **Updated:** 31 Dec 2024
- **Also known as:** GHSA-cxpg-8frp-cv2x

## What is CVE-2024-13040?

CVE-2024-13040 is a high-severity authentication bypass vulnerability in Quanta Computer QOCA aim, published on 31 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The QOCA aim from Quanta Computer has an Authorization Bypass Through User-Controlled Key vulnerability. By controlling the user ID parameter, remote attackers with regular privileges could access certain features as any user, modify any user's account information and privileges, leading to privilege escalation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2024-13040 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13040 is a high-severity authentication bypass vulnerability in Quanta Computer QOCA aim, published on 31 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13040 in the wild and no public exploit code.

Affected product: Quanta Computer QOCA aim. 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-13040/ (Markdown: https://insights.sbomify.com/CVE-2024-13040/index.md)
```

## Sources

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

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