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

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

What should Security Operations teams take away from the IBM X-Force 2024 Threat Intelligence Index?

3 min read - The IBM X-Force 2024 Threat Intelligence Index has been released. The headlines are in and among them are the fact that a global identity crisis is emerging. X-Force noted a 71% increase year-to-year in attacks using valid credentials.In this blog post, I’ll explore three cybersecurity recommendations from the Threat Intelligence Index, and define a checklist your Security Operations Center (SOC) should consider as you help your organization manage identity risk.The report identified six action items:Remove identity silosReduce the risk of…

Obtaining security clearance: Hurdles and requirements

3 min read - As security moves closer to the top of the operational priority list for private and public organizations, needing to obtain a security clearance for jobs is more commonplace. Security clearance is a prerequisite for a wide range of roles, especially those related to national security and defense.Obtaining that clearance, however, is far from simple. The process often involves scrutinizing one’s background, financial history and even personal character. Let’s briefly explore some of the hurdles, expectations and requirements of obtaining a…

Topic updates

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