Summary
A critical access-control vulnerability in the TOTOLINK T6 allows unauthenticated attackers to invoke the wireless-client disconnection function through the device's MQTT broker component.
By sending a specially crafted MQTT message, an attacker may forcibly disconnect wireless clients, disrupting network availability without valid credentials.
Affected context
The issue occurs in TOTOLINK T6 devices where the cs_broker MQTT component can reach the freeStaClient function without adequately verifying authorization. Deployments are at greater risk when the MQTT service is reachable by untrusted network users and management or broker interfaces are not isolated from general network access.
Exploit preconditions
- Attack surface: The device's MQTT broker component
- Required access: Network reachability to the relevant MQTT service; valid authentication may not be required
- Trigger point: Processing of a crafted MQTT message that invokes the client-disconnection functionality
- Why exploitation is possible: The function does not sufficiently enforce access control before performing a disruptive wireless-management operation
Why this happens
The vulnerability results from an authorization failure in the freeStaClient function. A network-facing message handler permits access to an administrative or disruptive operation without first establishing that the requester is authorized to perform it.
This behavior maps to CWE-284: Improper Access Control, in which protected functionality is exposed without effective enforcement of the intended security policy.
Potential impact
- Unauthenticated attackers may disconnect wireless clients
- Users may experience loss of network connectivity
- Repeated requests could cause sustained wireless denial of service
- Connected devices and dependent services could become intermittently unavailable
- Administrators may face operational disruption during an attack
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the function boundary and reducing exposure of administrative messaging interfaces.
Common defensive patterns include:
- Require authenticated and authorized sessions before allowing client-management operations
- Apply deny-by-default access policies to MQTT topics and commands
- Isolate broker and device-management services from untrusted network segments
- Restrict management operations according to least privilege
- Validate message origin, command scope, and intended target before execution
- Use rate limits and monitoring for repeated client-disconnection requests
- Disable unnecessary broker exposure where the deployment does not require it
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis of MQTT handlers for calls to administrative functions without nearby authorization checks
- Code review signals such as unauthenticated message callbacks invoking network or device-control operations
- Tests that attempt privileged MQTT actions from anonymous or low-privilege sessions
- Broker policy reviews verifying topic-level authentication, authorization, and network isolation
- Runtime monitoring for repeated client-disconnection commands or unusual MQTT activity
- Automated security review tools that identify missing authorization checks on externally reachable functions

