# CVE-2017-9138: Command injection in n/a

> Attackers with local network access can execute arbitrary shell commands and modify credentials via a debug interface on Tenda routers.

- **Severity:** High 8.0 (`CVSS:3.0/AV:A/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:** 21 May 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9r56-m5wr-p8gc

## What is CVE-2017-9138?

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

### Official description

There is a debug-interface vulnerability on some Tenda routers (FH1202/F1202/F1200: versions before 1.2.0.20). After connecting locally to a router in a wired or wireless manner, one can bypass intended access restrictions by sending shell commands directly and reading their results, or by entering shell commands that change this router's username and password.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-9138?

It affects 3 products.


Products: Tendacn F1200 Firmware, Tendacn F1202 Firmware, Tendacn Fh1202 Firmware.

## How do I fix CVE-2017-9138?

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

## Is CVE-2017-9138 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9139](https://insights.sbomify.com/CVE-2017-9139/): Memory corruption in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9138 and fix it if it is affected.

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

## Sources

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

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