# CVE-2023-41011: Command injection in n/a

> Remote attackers can execute arbitrary code on China Mobile Intelligent Home Gateways via the shortcut_telnet.cg component.

- **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:** 14 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-733h-qv2x-3845

## What is CVE-2023-41011?

CVE-2023-41011 is a critical command injection vulnerability in n/a, published on 14 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Command Execution vulnerability in China Mobile Communications China Mobile Intelligent Home Gateway v.HG6543C4 allows a remote attacker to execute arbitrary code via the shortcut_telnet.cg component.

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

## Which versions are affected by CVE-2023-41011?

It affects 1 product.


Products: Chinamobile Intelligent Home Gateway Firmware.

## How do I fix CVE-2023-41011?

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

## Is CVE-2023-41011 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-41012](https://insights.sbomify.com/CVE-2023-41012/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41011 and fix it if it is affected.

What it is: CVE-2023-41011 is a critical command injection vulnerability in n/a, published on 14 Sep 2023. 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-2023-41011 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-2023-41011/ (Markdown: https://insights.sbomify.com/CVE-2023-41011/index.md)
```

## Sources

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

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