# CVE-2021-34539: Command injection in n/a

> High-privileged users can execute arbitrary code by setting an unintended executable path due to lack of validation in the Java Version setting.

- **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:** 10 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vp24-gcm3-2g97

## What is CVE-2021-34539?

CVE-2021-34539 is a high-severity command injection vulnerability in n/a, published on 10 Jun 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in CubeCoders AMP before 2.1.1.8. A lack of validation of the Java Version setting means that an unintended executable path can be set. The result is that high-privileged users can trigger code execution.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2021-34539?

It affects 1 product.


Products: Cubecoders Amp.

## How do I fix CVE-2021-34539?

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

## Is CVE-2021-34539 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-31926](https://insights.sbomify.com/CVE-2021-31926/): Missing authorization in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34539 and fix it if it is affected.

What it is: CVE-2021-34539 is a high-severity command injection vulnerability in n/a, published on 10 Jun 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-34539 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-2021-34539/ (Markdown: https://insights.sbomify.com/CVE-2021-34539/index.md)
```

## Sources

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

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