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

> Unauthenticated attackers can upload large files to exhaust disk space, causing a denial of service in Zephyr Enterprise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2023
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-fxfj-7524-fg7p

## What is CVE-2023-22890?

CVE-2023-22890 is a high-severity vulnerability in n/a, published on 8 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SmartBear Zephyr Enterprise through 7.15.0 allows unauthenticated users to upload large files, which could exhaust the local drive space, causing a denial of service condition.

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

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

It affects 1 product.


Products: Smartbear Zephyr Enterprise.

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

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

## Is CVE-2023-22890 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-22889](https://insights.sbomify.com/CVE-2023-22889/): Code injection in n/a (critical 9.8)
- [CVE-2023-22891](https://insights.sbomify.com/CVE-2023-22891/): Privilege escalation in n/a (high 8.1)
- [CVE-2023-22892](https://insights.sbomify.com/CVE-2023-22892/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22890 is a high-severity vulnerability in n/a, published on 8 Mar 2023. 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-2023-22890 in the wild and no public exploit code.

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

## Sources

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

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