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

> Remote attackers can execute arbitrary Java code by uploading malicious applications to the General Bytes Crypto Application Server.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-vxx2-f897-g654

## What is CVE-2023-28725?

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

### Official description

General Bytes Crypto Application Server (CAS) 20230120, as distributed with General Bytes BATM devices, allows remote attackers to execute arbitrary Java code by uploading a Java application to the /batm/app/admin/standalone/deployments directory, aka BATM-4780, as exploited in the wild in March 2023. This is fixed in 20221118.48 and 20230120.44.

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

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

It affects 1 product.


Products: Generalbytes Crypto Application Server.

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

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

## Is CVE-2023-28725 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-28725 is a critical vulnerability in n/a, published on 21 Mar 2023. 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-2023-28725 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-28725/ (Markdown: https://insights.sbomify.com/CVE-2023-28725/index.md)
```

## Sources

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

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