# CVE-2022-37027: Code injection in n/a

> Authenticated administrators can inject Java JVM options to enable JMX, leading to remote code execution as the system user.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-8wrc-9xqr-5ph9

## What is CVE-2022-37027?

CVE-2022-37027 is a high-severity code injection vulnerability in n/a, published on 21 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Ahsay AhsayCBS 9.1.4.0 allows an authenticated system user to inject arbitrary Java JVM options. Administrators that can modify the Runtime Options in the web interface can inject Java Runtime Options. These take effect after a restart. For example, an attacker can enable JMX services and consequently achieve remote code execution as the system user.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Ahsay Cloud Backup Suite.

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

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

## Is CVE-2022-37027 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-105134](https://insights.sbomify.com/CVE-2026-105134/): Ahsay AhsayCBS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2026-105133](https://insights.sbomify.com/CVE-2026-105133/): Ahsay AhsayCBS Improper Authentication (medium 6.9, exploited in the wild)
- [CVE-2020-5846](https://insights.sbomify.com/CVE-2020-5846/): File upload in n/a (high 8.8)
- [CVE-2019-10267](https://insights.sbomify.com/CVE-2019-10267/): File upload in n/a (high 8.8)
- [CVE-2019-10265](https://insights.sbomify.com/CVE-2019-10265/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37027 is a high-severity code injection vulnerability in n/a, published on 21 Sep 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-37027 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-37027/ (Markdown: https://insights.sbomify.com/CVE-2022-37027/index.md)
```

## Sources

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

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