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

> An authenticated attacker can execute arbitrary commands via the set password function in the admin email settings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 17 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-pm74-5m4v-fxfg

## What is CVE-2021-34164?

CVE-2021-34164 is a high-severity command injection vulnerability in n/a, published on 17 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Permissions vulnerability in LIZHIFAKA v.2.2.0 allows authenticated attacker to execute arbitrary commands via the set password function in the admin/index/email location.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Lizhifaka Project Lizhifaka.

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

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

## Is CVE-2021-34164 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-34164 is a high-severity command injection vulnerability in n/a, published on 17 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-34164 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-2021-34164/ (Markdown: https://insights.sbomify.com/CVE-2021-34164/index.md)
```

## Sources

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

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