# CVE-2024-22663: Command injection in n/a

> Attackers can execute arbitrary commands on TOTOLINK A3700R routers via the setOpModeCfg parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 23 Jan 2024
- **Updated:** 30 May 2025
- **Also known as:** GHSA-5rh9-65g2-hc9h

## What is CVE-2024-22663?

CVE-2024-22663 is a critical command injection vulnerability in n/a, published on 23 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TOTOLINK_A3700R_V9.1.2u.6165_20211012has a command Injection vulnerability via setOpModeCfg

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-22663?

It affects 1 product.


Products: Totolink A3700r Firmware.

## How do I fix CVE-2024-22663?

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

## Is CVE-2024-22663 being exploited?

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

## 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-2024-22663 and fix it if it is affected.

What it is: CVE-2024-22663 is a critical command injection vulnerability in n/a, published on 23 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22663 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-2024-22663/ (Markdown: https://insights.sbomify.com/CVE-2024-22663/index.md)
```

## Sources

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

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