# CVE-2023-42335: File upload in n/a

> Remote attackers can execute arbitrary code via unrestricted file upload in the New Expense component of Fl3xx Dispatch and Crew.

- **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:** 20 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-h5vh-xqgr-2q2g

## What is CVE-2023-42335?

CVE-2023-42335 is a high-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

Unrestricted File Upload vulnerability in Fl3xx Dispatch 2.10.37 and fl3xx Crew 2.10.37 allows a remote attacker to execute arbitrary code via the add attachment function in the New Expense component.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 2 products.


Products: Fl3xx Crew, Fl3xx Dispatch.

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

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

## Is CVE-2023-42335 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-42334](https://insights.sbomify.com/CVE-2023-42334/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42335 is a high-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-42335 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-42335/ (Markdown: https://insights.sbomify.com/CVE-2023-42335/index.md)
```

## Sources

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

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