March 6, 2017 By Larry Loeb 2 min read

A recent report raised concerns about the security of certain devices manufactured by a company called DblTek. Trustwave SpiderLabs issued a report on a backdoor password scheme it found rampant in DblTek GoIP GSM gateways and other products that allow a remote user root-level Telnet access to the device. The attacker would then be able to execute arbitrary code and gain full control of the device.

A Widespread Occurrence

Hong Kong-based DblTek manufactures IP phones, SIM servers, various voice-over-IP (VoIP) equipment and cross-network gateways, noted Bleeping Computer. Gateways are often used by VoIP and telcom providers to link GSM and classic IP networks together. Trustwave confirmed that the GoIP 1, 4, 8, 16 and 32 models of the gateway all contain the potentially dangerous backdoor.

Other DblTek products were not vulnerability tested by the researchers, but they did not rule out that the problem could be larger than just the gateways.

The Hidden Account

Trustwave found that an account named “dbladm” was present on the gateway device firmware and was not controlled through the administration console. This hidden account can provide root-level access to the device, yet is not included in any documentation. Neither are the default “ctlcmd” and “limitsh” Telnet accounts.

This account also runs differently than the default accounts. Instead of using a traditional password, the hidden account uses a proprietary challenge-response authentication scheme for protection. This method of authentication gives the user a string. The user then performs various operations on that string to discover the password needed to continue.

This lends itself to an automated attack that is fairly simple to perform. An attacker could develop automated scripts to read the challenge and compute the response, thereby authenticating themselves on the device through the backdoor password.

Why Is the Backdoor Password Available?

Trustwave reported this situation to the vendor on Oct. 13, 2016. DblTek responded by issuing a patched version of the firmware on Dec. 22, 2016. But this patch does not eliminate the dbladm account from the gateway firmware; it just makes the authentication for it slightly more complex.

“It seems DblTek engineers did not understand that the issue is the presence of a flawed challenge response mechanism and not the difficulty of reverse engineering it,” stated Trustwave.

Why would the company keep such a backdoor? It may be a special account needed for testing devices, which has happened with other telcom products. Indeed, when activated, the account will send several UDP packets directed to the IP address 192.168.2.1 on port 11000/udp, Trustwave explained. This is consistent with the actions of a test account.

However, the DblTek response to not properly seal this particular vulnerability even when notified indicated that, for whatever reason, it wants the backdoor to exist — even if it slightly more obscured. Gateway users need to be aware of the potential vulnerability present in their equipment and deal with it accordingly.

More from

Hive0137 and AI-supplemented malware distribution

12 min read - IBM X-Force tracks dozens of threat actor groups. One group in particular, tracked by X-Force as Hive0137, has been a highly active malware distributor since at least October 2023. Nominated by X-Force as having the “Most Complex Infection Chain” in a campaign in 2023, Hive0137 campaigns deliver DarkGate, NetSupport, T34-Loader and Pikabot malware payloads, some of which are likely used for initial access in ransomware attacks. The crypters used in the infection chains also suggest a close relationship with former…

Unveiling the latest banking trojan threats in LATAM

9 min read - This post was made possible through the research contributions of Amir Gendler.In our most recent research in the Latin American (LATAM) region, we at IBM Security Lab have observed a surge in campaigns linked with malicious Chrome extensions. These campaigns primarily target Latin America, with a particular emphasis on its financial institutions.In this blog post, we’ll shed light on the group responsible for disseminating this campaign. We’ll delve into the method of web injects and Man in the Browser, and…

Crisis communication: What NOT to do

4 min read - Read the 1st blog in this series, Cybersecurity crisis communication: What to doWhen an organization experiences a cyberattack, tensions are high, customers are concerned and the business is typically not operating at full capacity. Every move you make at this point makes a difference to your company’s future, and even a seemingly small mistake can cause permanent reputational damage.Because of the stress and many moving parts that are involved, businesses often fall short when it comes to communication in a crisis.…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today