CVE-2017-20204
CWE-1242Published: October 15, 2025· Updated: Jun 17, 2026
Official Description
DBLTek GoIP devices (models GoIP 1, 4, 8, 16, and 32) contain an undocumented vendor backdoor in the Telnet administrative interface that allows remote authentication as an undocumented user via a proprietary challenge–response scheme which is fundamentally flawed. Because the challenge response can be computed from the challenge itself, a remote attacker can authenticate without knowledge of a secret and obtain a root shell on the device. This can lead to persistent remote code execution, full device compromise, and arbitrary control of the device and any managed services. The firmware used within these devices was updated in December 2016 to make this vulnerability more complex to exploit. However, it is unknown if DBLTek has taken steps to fully mitigate.
Risk Analysis
DBLTek GoIP devices (models 1, 4, 8, 16, and 32) have an undocumented vendor backdoor in their Telnet interface. A flawed challenge-response scheme allows remote attackers to authenticate without a secret, gaining a root shell. This critical vulnerability, with a CVSS score of 9.3, can lead to persistent remote code execution and full device compromise.
No public exploit is currently known for this vulnerability. It is remotely exploitable due to the network attack vector and low attack complexity.
It is unknown if DBLTek has fully mitigated this vulnerability. If possible, restrict Telnet access to GoIP devices or disable it entirely. Monitor network traffic for suspicious activity originating from these devices.
Technical Analysis
CVE-2017-20204 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.
The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.
CVSS v3.1 Vector Breakdown
Exploit & PoC Resources
All References (4)
Quick Facts
Related CVEs (CWE-1242)
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2017-20204 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts