CVE-2017-9138
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTenda routers (FH1202, F1202, F1200) versions before 1.2.0.20 contain a debug interface that allows any locally connected user (wired or wireless) to bypass intended access restrictions. Attackers can send shell commands directly to the system and read results, or modify router credentials by entering specific shell commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.2.0.19<= 1.2.0.19<= 1.2.0.19CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLog into the router web interface (typically at 192.168.0.1 or 192.168.1.1) and check the device information page, or physically inspect the router label for model number (F1200, FH1202, or F1202)Affected if Router model is Tenda F1200, FH1202, or F1202
-
Check firmware versionIn the router web interface, navigate to System Settings or Status page to find the firmware version. Alternatively, access the page at /goform/getSysInfo or similar endpoint via HTTP GETAffected if Firmware version is 1.2.0.19 or lower (before 1.2.0.20)
-
Test for debug interface accessibilitySend an HTTP GET request to the debug endpoint. Common paths include /debug.htm, /debug.jsp, or /cgi-bin/debug. Use curl or browser to request http://router_ip/debug.htmAffected if Debug interface page loads and accepts input without authentication or after initial login
-
Verify debug command execution capabilityIf debug page is accessible, attempt to send a simple shell command via the interface (such as viewing system information) to confirm the command injection/ execution capability existsAffected if Debug interface accepts and executes shell commands without additional authentication beyond local network access
You are affected if you own a Tenda F1200, FH1202, or F1202 router running firmware version 1.2.0.19 or earlier, and the debug interface is accessible from your local network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade router firmware to version 1.2.0.20 or later. If updating is not possible, ensure strong physical and network access controls and disable any exposed debug or administrative interfaces.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-9138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data