Summary
Mercusys AC12G (EU) V1 routers running firmware AC12G(EU)_V1_200909 expose a TDDP password change endpoint that does not enforce rate limiting or lockout controls.
An attacker on the adjacent network can send unlimited password guesses to this endpoint without authentication, enabling practical brute-force attacks against the router's administrative credentials.
Affected context
This vulnerability occurs in the router's TDDP (TP-Link Device Debug Protocol or similar management/debug interface) password change functionality, specifically at the endpoint identified as code=10.
While the normal login endpoint (code=7) applies rate limiting and account lockout protections, the password change endpoint does not.
The issue is relevant when:
- The router is running firmware AC12G(EU)_V1_200909
- TDDP or related management services are reachable from the local or adjacent network segment
- Administrative credentials protect critical configuration and network security settings
Exploit preconditions
- Attack surface: Network-accessible management/debug interface (TDDP) exposed by the router.
- Network location: Attacker must be on the adjacent network (e.g., same LAN, Wi-Fi network, or otherwise able to reach the router's management IP).
- Authentication: Not required; the vulnerable TDDP password change endpoint can be interacted with without prior login.
- Trigger point: Sending repeated requests to the
code=10endpoint to repeatedly guess or influence the administrative password. - Why exploitation is possible: The password change functionality does not inherit or implement the rate limiting, lockout, or brute-force protections configured on the standard login endpoint (
code=7), allowing unlimited guessing attempts.
Why this happens
The core issue is a missing enforcement of authentication throttling and lockout rules on a sensitive management endpoint.
While the primary login endpoint is protected by rate limiting, the TDDP password change endpoint is implemented as a separate code path that lacks equivalent controls.
This discrepancy maps to CWE-307: Improper Restriction of Excessive Authentication Attempts, where a component fails to cap or delay repeated authentication-related operations, enabling automated brute-force attacks.
Architecturally, the bug reflects inconsistent security policies across related authentication flows: one endpoint enforces limits while another, equally sensitive, does not.
Potential impact
- Unauthorized guessing of the router's administrative password via brute force
- Full compromise of the router's web and/or management interface once credentials are obtained
- Modification of DNS, routing, and firewall settings, enabling traffic interception or redirection
- Disabling of security features such as Wi-Fi encryption, guest networks, or parental controls
- Use of the compromised router as a foothold for further attacks within the local network
General mitigation guidance
Mitigation focuses on aligning brute-force protections across all authentication and credential management paths.
General defensive patterns include:
- Applying consistent rate limiting and lockout policies to all endpoints that set, change, or validate credentials, including debugging or auxiliary protocols.
- Introducing exponential backoff, request throttling, or CAPTCHA-style friction for repeated password-related requests from the same source.
- Centralizing authentication and password management logic so that all code paths share the same security controls rather than duplicating logic per endpoint.
- Restricting management interfaces to trusted networks only (e.g., disabling exposure over Wi-Fi guest networks or untrusted VLANs).
- Encouraging strong, high-entropy administrative passwords to raise the cost and time required for brute-force attempts.
How teams detect issues like this
Detection and assurance can be improved through:
- Code review: Verifying that every endpoint that reads, validates, or changes credentials uses shared middleware or libraries for rate limiting and lockout, and that no separate "debug" or "maintenance" endpoints bypass these controls.
- Static analysis: Searching for password-change or authentication-related handlers that lack calls into the common throttling/rate-limiting routines, or that implement custom logic instead of shared security components.
- Configuration and integration testing: Running automated tests that perform repeated password attempts across all management endpoints to confirm lockout and throttling behaviors are uniformly enforced.
- Network monitoring: Using intrusion detection or log analysis to flag abnormal volumes of password-related requests to internal management interfaces, even when they do not trigger built-in limits.

