Summary
Tenda AX12 Pro V2 routers contain hard-coded credentials within the Telnet service, allowing authentication with fixed, embedded accounts.
Under certain remote conditions, an attacker who can reach the Telnet interface may be able to log in using these credentials, bypassing normal access controls and gaining privileged access to the device.
Affected context
This vulnerability affects Tenda AX12 Pro V2 (16.03.49.24_cn) devices that expose or enable the Telnet service, whether intentionally (for administration) or unintentionally through misconfiguration or default settings.
The risk materializes when:
- The Telnet service is reachable from an attacker-controlled network segment (e.g., LAN or, worse, the internet).
- The device uses static, embedded credentials that cannot be easily changed by administrators.
- Network segmentation or management-plane isolation is weak or absent.
Exploit preconditions
- Attack surface: Network-accessible Telnet interface on the Tenda AX12 Pro V2.
- Required access: Network-level access to the router's Telnet port (typically TCP/23) from the same LAN or a reachable network path.
- Trigger point: Initiating a Telnet connection and attempting authentication using hard-coded credentials.
- Why exploitation is possible: The authentication logic relies on fixed, built-in credentials (or equivalent secrets) instead of credentials fully controlled by the administrator. Once these are discovered or reverse-engineered, any party with Telnet access can reuse them, bypassing intended authentication controls. The attack has high complexity because the credentials and conditions to exploit may be non-trivial to obtain and require specific knowledge or circumstances.
Why this happens
The underlying issue is the presence of hard-coded credentials in the Telnet service implementation, consistent with:
- CWE-259: Use of Hard-coded Password
- CWE-798: Use of Hard-coded Credentials
Instead of relying solely on operator-managed passwords or keys, the firmware embeds fixed credentials (or equivalent secret tokens) in code or configuration. When the service uses these credentials for authentication, any party that learns them—through reverse engineering, analysis of leaked configuration, or public exploit code—can authenticate as a privileged user. This breaks the assumption that only authorized administrators know the management credentials and undermines the security boundary of the device's management plane.
Potential impact
- Remote login to the router's Telnet interface using non-changeable or poorly protected credentials.
- Full administrative control of the device, including configuration changes and firmware manipulation.
- Interception, modification, or redirection of network traffic routed through the device.
- Deployment of persistent malware or backdoors at the network edge.
- Use of the router as a foothold for lateral movement into internal networks.
- Enrollment of the device into botnets or participation in DDoS attacks.
General mitigation guidance
Risk reduction focuses on eliminating implicit trust in embedded credentials and limiting exposure of legacy management services:
- Prefer disabling Telnet entirely and using more secure, audited management protocols (e.g., HTTPS-based web UI with strong authentication).
- Where Telnet or similar services are unavoidable, require administrator-configured, unique credentials and avoid any fallback to hard-coded accounts or default secrets.
- Apply network-level controls: restrict management access to a dedicated management VLAN, use firewall rules to block Telnet from untrusted networks, and avoid exposing Telnet to the internet.
- Enforce least privilege: ensure that service accounts used for management have only the permissions strictly necessary.
- Design firmware so that all authentication secrets are externalized (e.g., in user-managed configuration) and never compiled directly into binaries or static configuration.
- Implement secure provisioning workflows that encourage or require users to set unique administrative passwords during initial setup.
How teams detect issues like this
Detection generally combines firmware analysis, behavioral monitoring, and configuration review:
- Static analysis / firmware review:
- Examine firmware images for embedded passwords, keys, or known credential strings in the Telnet daemon or related binaries.
- Use code scanning rules that flag use of literal passwords, static token values, or vendor backdoor accounts in authentication logic.
- Configuration and network monitoring:
- Periodically scan internal networks for exposed Telnet services on routers and verify that they are disabled or restricted.
- Monitor authentication logs (where available) for repeated successful logins from unexpected hosts or accounts that are not user-configured.
- Policy enforcement:
- Enforce network security policies that prohibit legacy services like Telnet on management interfaces unless explicitly approved.
- Integrate automated checks in device hardening baselines to confirm that remote management is only available via secure channels and that default credentials are disabled.
- Third-party tooling:
- Use IoT/firmware security scanners capable of identifying hard-coded credentials and management backdoors before deployment.

