# CVE-2022-29936: Deserialization in n/a

> Authenticated users can achieve remote code execution via unsafe Java deserialization in the file upload endpoint.

- **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:** 29 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3mrf-6r8f-wh4j

## What is CVE-2022-29936?

CVE-2022-29936 is a high-severity unsafe deserialization vulnerability in n/a, published on 29 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

USU Oracle Optimization before 5.17 allows authenticated quantum users to achieve remote code execution because of /v2/quantum/save-data-upload-big-file Java deserialization. NOTE: this is not an Oracle Corporation product.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2022-29936?

It affects 1 product.


Products: Usu Oracle Optimization.

## How do I fix CVE-2022-29936?

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

## Is CVE-2022-29936 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29937](https://insights.sbomify.com/CVE-2022-29937/): Command injection in n/a (high 8.8)
- [CVE-2022-29934](https://insights.sbomify.com/CVE-2022-29934/): Missing authorization in n/a (high 7.8)
- [CVE-2022-29935](https://insights.sbomify.com/CVE-2022-29935/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29936 and fix it if it is affected.

What it is: CVE-2022-29936 is a high-severity unsafe deserialization vulnerability in n/a, published on 29 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29936 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-2022-29936/ (Markdown: https://insights.sbomify.com/CVE-2022-29936/index.md)
```

## Sources

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

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