# CVE-2022-37425: Command injection in n/a

> Attackers can execute arbitrary code via the FILES directive in VM templates, leading to remote code execution on OpenNebula core.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 28 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hw6h-8grh-49hp, UBUNTU-CVE-2022-37425

## What is CVE-2022-37425?

CVE-2022-37425 is a critical command injection vulnerability in n/a, published on 28 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in OpenNebula OpenNebula core on Linux allows Remote Code Inclusion.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Opennebula Opennebula.

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

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

## Is CVE-2022-37425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37424](https://insights.sbomify.com/CVE-2022-37424/): Information disclosure in n/a (medium 6.5)
- [CVE-2025-56534](https://insights.sbomify.com/CVE-2025-56534/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-56535](https://insights.sbomify.com/CVE-2025-56535/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-56536](https://insights.sbomify.com/CVE-2025-56536/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2025-56537](https://insights.sbomify.com/CVE-2025-56537/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37425 is a critical command injection vulnerability in n/a, published on 28 Oct 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-37425 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-37425/ (Markdown: https://insights.sbomify.com/CVE-2022-37425/index.md)
```

## Sources

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

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