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

> Attackers can execute arbitrary commands via the package manager by manipulating the pkg parameter in update requests, leading to code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 18 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7qw8-c2p4-4gxq

## What is CVE-2021-30070?

CVE-2021-30070 is a high-severity command injection vulnerability in n/a, published on 18 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in HestiaCP before v1.3.5. Attackers are able to arbitrarily install packages due to values taken from the pgk [] parameter in the update request being transmitted to the operating system's package manager.

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

It affects 1 product.


Products: Hestiacp Hestiacp.

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

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

## Is CVE-2021-30070 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-5084](https://insights.sbomify.com/CVE-2023-5084/): Cross-site Scripting (XSS) - Reflected in hestiacp/hestiacp (low 3.9)
- [CVE-2023-4517](https://insights.sbomify.com/CVE-2023-4517/): Cross-site Scripting (XSS) - Stored in hestiacp/hestiacp (low 3.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30070 is a high-severity command injection vulnerability in n/a, published on 18 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-30070 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-30070/ (Markdown: https://insights.sbomify.com/CVE-2021-30070/index.md)
```

## Sources

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

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