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

> Attackers can execute arbitrary commands on TOTOLINK A3700R routers via the FileName parameter in the firmware upload function.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qqhv-2h68-rx7f

## What is CVE-2022-36460?

CVE-2022-36460 is a high-severity command injection vulnerability in n/a, published on 25 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TOTOLINK A3700R V9.1.2u.6134_B20201202 was discovered to contain a command injection vulnerability via the FileName parameter in the function UploadFirmwareFile.

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

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

It affects 1 product.


Products: Totolink A3700r Firmware.

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

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

## Is CVE-2022-36460 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-42545](https://insights.sbomify.com/CVE-2024-42545/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-37637](https://insights.sbomify.com/CVE-2024-37637/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-37634](https://insights.sbomify.com/CVE-2024-37634/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-37635](https://insights.sbomify.com/CVE-2024-37635/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-22660](https://insights.sbomify.com/CVE-2024-22660/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36460 is a high-severity command injection vulnerability in n/a, published on 25 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36460 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-36460/ (Markdown: https://insights.sbomify.com/CVE-2022-36460/index.md)
```

## Sources

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

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