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

> An attacker with a valid token can execute shell commands on the web server via shell metacharacter injection in the test result page.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q52p-wrc3-9p77

## What is CVE-2021-35062?

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

### Official description

A Shell Metacharacter Injection vulnerability in result.php in DRK Odenwaldkreis Testerfassung March-2021 allow an attacker with a valid token of a COVID-19 test result to execute shell commands with the permissions of the web server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Testzentrum-Odw Testerfassung.

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

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

## Is CVE-2021-35062 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-35062 is a high-severity command injection vulnerability in n/a, published on 30 Aug 2021. 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-35062 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-35062/ (Markdown: https://insights.sbomify.com/CVE-2021-35062/index.md)
```

## Sources

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

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