Severity:

CRITICAL RISK

(9.8)

Command Injection (CWE-77) in Totolink A7100RU API

CVE-2026-6113

Deferred

Vulnerability type

Category:

Command Injection

CWE:

CWE-77, CWE-78

Impact:

Potential Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical command injection vulnerability affects the setTtyServiceCfg function in Totolink A7100RU firmware. If attacker-controlled input reaches this function without adequate filtering or isolation, an attacker may cause unintended commands to be interpreted by the device.

Affected context

The vulnerability occurs in the Totolink A7100RU 7.4cu.2313_b20191024 firmware, specifically within the setTtyServiceCfg functionality. Risk depends on whether the function is reachable through an exposed management interface, whether authentication is enforced, and whether supplied values are incorporated into operating-system command processing.

Exploit preconditions

  • Attack surface: A router management or service interface exposing setTtyServiceCfg
  • Required access: Access sufficient to invoke the affected function; the exact authentication requirement depends on deployment and interface configuration
  • Trigger point: Processing of configuration data by setTtyServiceCfg
  • Why exploitation is possible: Insufficient separation between configuration input and command interpretation may allow attacker-controlled data to influence command execution

Why this happens

The underlying bug is a command injection condition in which externally influenced input is passed into an operating-system command context without reliable separation, validation, or escaping. This maps to CWE-77: Improper Neutralization of Special Elements used in a Command, with CWE-78 also relevant where the affected behavior results in operating-system command execution.

Potential impact

  • An attacker may execute unauthorized commands with the privileges of the affected service
  • The device could be reconfigured, disabled, or used to alter network traffic
  • Sensitive configuration data may be exposed
  • The router may be incorporated into a botnet or used for lateral movement
  • Other connected systems could be placed at risk

General mitigation guidance

Mitigation generally focuses on removing shell interpretation from configuration workflows and reducing trust in management input.

Common defensive patterns include:

  • Prefer structured APIs and direct system calls over shell commands
  • Apply strict allowlists for configuration values and reject unexpected characters or formats
  • Keep administrative interfaces isolated from untrusted networks
  • Require strong authentication and least-privilege service permissions
  • Restrict outbound access and unnecessary local capabilities from router services
  • Treat all management parameters as untrusted until validated at the appropriate boundary

How teams detect issues like this

Organizations can assess for this weakness through:

  • Static analysis rules identifying user-controlled data passed to shell execution or command-construction APIs
  • Code review checks for string concatenation or interpolation in system command paths
  • Tests using boundary values and command-metacharacter handling, without relying on destructive payloads
  • Network monitoring for unexpected administrative requests or unusual router-initiated connections
  • Policy enforcement requiring allowlisted configuration schemas and authenticated management access
  • Automated security review tools that flag command execution reachable from request parameters

Sources

SourceLink
github.comgithub.com/Litengzheng/vuldb_new/blob/main/A7100RU/vul_178/README.md
vuldb.comvuldb.com/submit/792246
vuldb.comvuldb.com/vuln/356973
vuldb.comvuldb.com/vuln/356973/cti
totolink.nettotolink.net/

Frequently asked

questions

It may be remotely exploitable when the affected management function is reachable over a network and the attacker can satisfy any required access controls. Exposure depends on the router's interface configuration and deployment context.

The available description does not establish the authentication requirement. The relevant determining factors are whether setTtyServiceCfg is exposed and what permissions are needed to invoke it.

Avoid passing configuration values through shell interpreters. Use structured parsing, strict allowlists, direct APIs, and least-privilege execution for any required system operations.

Treat management input as untrusted, enforce authenticated and isolated administration, review command-construction code, and apply static analysis and security testing to device firmware.

Find out what's already
exploitable in your codebase.