# CVE-2022-36431: File upload in n/a

> Unauthenticated attackers can execute arbitrary code by uploading a crafted JSP file in Rocket TRUfusion Enterprise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-hccp-2vx9-gv82

## What is CVE-2022-36431?

CVE-2022-36431 is a critical vulnerability in n/a, published on 1 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file upload vulnerability in Rocket TRUfusion Enterprise before 7.9.6.1 allows unauthenticated attackers to execute arbitrary code via a crafted JSP file. Issue fixed in version 7.9.6.1.

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

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

It affects 1 product.


Products: Rocketsoftware Trufusion.

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

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

## Is CVE-2022-36431 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36431 is a critical vulnerability in n/a, published on 1 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36431 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-2022-36431/ (Markdown: https://insights.sbomify.com/CVE-2022-36431/index.md)
```

## Sources

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

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