dbcve.org
F460Hardware / appliance · Zte

CVE-2014-2321

HIGH · 10.0 CVSS v2.0 Published 2014-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click

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 · unedited
web_shell_cmd.gch on ZTE F460 and F660 cable modems allows remote attackers to obtain administrative access via sendcmd requests, as demonstrated by using "set TelnetCfg" commands to enable a TELNET service with specified credentials.

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 confidence

The ZTE F460 and F660 cable modems contain a vulnerability in the web_shell_cmd.gch endpoint that allows remote attackers to execute sendcmd requests without proper authorization. Attackers can send 'set TelnetCfg' commands to enable the TELNET service with attacker-specified credentials, achieving full administrative access to the device.

MitigationDisable remote management interfaces on the affected modems, block HTTP/HTTPS access from untrusted networks at the perimeter, and replace affected legacy devices with updated hardware that receives security patches.

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
F460Hardware / appliance
Affected:all versions
F660Hardware / appliance
Affected:all versions

CVSS 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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check the device label, web interface, or SNMP for model number F460 or F660
    Affected if Device is a ZTE F460 or F660 cable modem
  2. Test web_shell_cmd.gch endpoint accessibility
    Send an HTTP request to http://<device_ip>/web_shell_cmd.gch and observe if the endpoint responds
    Affected if The endpoint is reachable and returns a response (indicates the vulnerable interface is exposed)
  3. Verify remote management exposure
    Check if the device web interface is accessible from untrusted networks or the WAN interface
    Affected if Remote HTTP/HTTPS management is enabled and reachable from outside trusted networks
  4. Confirm TELNET service status
    Attempt to connect to port 23 on the device or check the device configuration for TELNET enable status
    Affected if TELNET service is enabled on the device (may indicate the vulnerability has been exploited)
  5. Review access logs for sendcmd activity
    Check device logs or network traffic logs for requests to web_shell_cmd.gch containing 'set TelnetCfg' or similar sendcmd commands
    Affected if Suspicious sendcmd requests targeting TelnetCfg are observed in logs

A user is affected if they operate a ZTE F460 or F660 device with the web_shell_cmd.gch endpoint exposed to untrusted networks, as this allows unauthorized remote administrative access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable remote management interfaces on the affected modems, block HTTP/HTTPS access from untrusted networks at the perimeter, and replace affected legacy devices with updated hardware that receives security patches.

Recommended fix High confidence
  1. This vulnerability is a hardcoded backdoor in the firmware web interface with no available vendor patch or firmware update.
  2. Contact your ISP to request a replacement device that receives security updates.
  3. If replacement is not possible, isolate the device on a dedicated network segment with strict firewall rules blocking all inbound access to the modem's web interface.
  4. Do not expose the cable modem's web management interface to the internet.
  5. Consider using your own router behind the ISP modem and disabling the ISP modem's routing functionality if possible.
Caveat These are end-of-life consumer cable modems with no security support from the vendor

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in F460 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-2321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2321 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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