Summary
TOTOLINK T6 contains an incorrect access-control implementation in the
setStaticDhcpRules function. An unauthenticated attacker may be able to add
or modify static DHCP rules by submitting a crafted request to the router's
CGI endpoint.
Affected context
The vulnerability occurs in TOTOLINK T6 firmware version 4.1.5cu.748_B20211015
when the static DHCP rule management function is reachable through the
device's web administration interface. Risk is greatest when the relevant
CGI endpoint is exposed to untrusted clients and the function does not
consistently enforce authentication or authorization before changing
configuration.
Exploit preconditions
- Attack surface: The router's CGI-based web management interface
- Required access: Network reachability to the affected endpoint; valid
administrative credentials may not be required
- Trigger point: Processing of requests handled by the
setStaticDhcpRules function
- Why exploitation is possible: The function permits configuration
changes without applying an adequate access-control check
Why this happens
The underlying bug is an authorization failure in a configuration-management
function. The application accepts a request intended to add or change static
DHCP rules without reliably verifying that the requester has the required
privileges. This behavior maps to CWE-284: Improper Access Control, in
which protected functionality or resources are not sufficiently restricted
to authorized subjects.
Potential impact
- An attacker may add unauthorized static DHCP assignments
- An attacker could redirect selected clients to unexpected network
addresses or services
- Network availability or local traffic behavior may be disrupted
- Malicious configuration changes can weaken trust in the router's DHCP
environment
- The device may become a stepping stone for further attacks against local
clients
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every
configuration-changing endpoint, rather than relying on the surrounding
interface or client-side controls.
Common defensive patterns include:
- Requiring authenticated, authorized sessions for all DHCP rule changes
- Applying server-side privilege checks before processing or persisting
configuration updates
- Rejecting requests that do not meet an explicit administrative policy
- Restricting management interfaces to trusted networks and administrative
paths
- Preserving least-privilege separation between read-only and
configuration-modifying operations
- Logging and reviewing changes to DHCP and other network-control settings
How teams detect issues like this
Organizations can look for this weakness through:
- Static analysis and code review of CGI handlers for missing authorization
checks before state-changing operations
- Tests that invoke configuration endpoints with unauthenticated and
lower-privilege sessions
- Web application policy checks requiring authentication and authorization
for all state-changing requests
- Network monitoring for unexpected requests to DHCP rule management
functions
- Audit-log review for static DHCP changes that lack a corresponding
authorized administrative action
Automated security review tools may help identify state-changing handlers
that do not enforce consistent access-control policies.

