# CVE-2023-42334: Privilege escalation in n/a

> A remote attacker can escalate privileges in Fl3xx Dispatch and Crew via an Indirect Object Reference vulnerability in the user parameter.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 20 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-m6jm-f5rm-2629

## What is CVE-2023-42334?

CVE-2023-42334 is a medium-severity vulnerability in n/a, published on 20 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Indirect Object Reference (IDOR) in Fl3xx Dispatch 2.10.37 and fl3xx Crew 2.10.37 allows a remote attacker to escalate privileges via the user parameter.

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

## Which versions are affected by CVE-2023-42334?

It affects 2 products.


Products: Fl3xx Crew, Fl3xx Dispatch.

## How do I fix CVE-2023-42334?

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

## Is CVE-2023-42334 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42334 exists.

## Other vulnerabilities in n/a

- [CVE-2023-42335](https://insights.sbomify.com/CVE-2023-42335/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42334 and fix it if it is affected.

What it is: CVE-2023-42334 is a medium-severity vulnerability in n/a, published on 20 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-42334 exists.

Affected product: n/a. 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-2023-42334/ (Markdown: https://insights.sbomify.com/CVE-2023-42334/index.md)
```

## Sources

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

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