Root shell access via hard-coded telnet credentials
Published Feb 2, 2023 · Updated Mar 26, 2025
Hard-coded credentials in TOTOLINK N200RE_v5 firmware 9.3.5u.6139 allow remote attackers to obtain root shell access over telnet. The web management handler accepts a crafted unauthenticated POST request that starts the telnet service, whose root account uses embedded credentials. Network reachability to the management interface is sufficient, and successful exploitation grants full command execution with root privileges.
Summary
What happened
Hard-coded credentials in TOTOLINK N200RE_v5 firmware 9.3.5u.6139 allow remote attackers to obtain root shell access over telnet. The web management handler accepts a crafted unauthenticated POST request that starts the telnet service, whose root account uses embedded credentials. Network reachability to the management interface is sufficient, and successful exploitation grants full command execution with root privileges.
The record
- CVE
- CVE-2022-48113
- Published
- Feb 2, 2023
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1078, T1059.008
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- TOTOLINK N200REv5 Telnet Backdoorproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo