Skip to content

About

Root shell access research on ZLT FWA equipment — W304VA PRO (IDU) & X17M (ODU), including binary analysis of the IDU/ODU management plane.

Resources

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ZLT FWA Shell Access — W304VA PRO (IDU) & X17M (ODU)

ZLT FWA

Security research notes. Tested on unspecified ISP deployment in Tunisia.

Background

I recently upgraded to a 100 Mbps up/down plan from 50 Mbps — the ISP swapped in a new router with it. I'd been fighting to unlock the old one (W51 + X16) with no luck; the U-Boot on that one was locked down tight and I couldn't do anything with it. Got lucky with this new unit: stumbled across a post on XDA Forums with some useful bootloader commands, and started following along. Hit some issues specific to this ISP's deployment that weren't covered there, which sent me down a research rabbit hole of my own.


Devices

Both units are manufactured by TOZED KANGWEI TECH Co., Ltd (Guangzhou, China) and deployed together as a fixed wireless access (FWA) bundle.

ZLT X17M — ODU (Outdoor Unit)

Form factor Outdoor 5G CPE, no Wi-Fi — mounts on roof, single PoE cable to IDU
Chipset Qualcomm Snapdragon X65 (SDX65)
5G NR (SA/NSA) N1/N3/N5/N7/N8/N20/N28/N38/N40/N41/N75/N76/N77/N78
LTE B1/B3/B5/B7/B8/B20/B28/B32/B38/B40/B41/B42/B43
WCDMA B1/B5/B8
Speed DL up to 4 Gbps / UL up to 1 Gbps; 4×4 DL MIMO, 2×2 UL MIMO
Antennas 11 dBi directional + omnidirectional
Port 1× RJ45 2.5 GbE (PoE 802.3bt input — data + power on one cable)
Enclosure IP67, −30°C to +65°C
Other eSIM, TR-069, VPN (IPSec / L2TP / PPTP / WireGuard), IPv4/IPv6 dual-stack

ZLT W304VA PRO — IDU (Indoor Unit)

Form factor Indoor desktop router, no cellular modem
CPU ARMv7 (SoC undisclosed), Linux 4.4.115
Wi-Fi Wi-Fi 6 (802.11ax) AX3000, dual-band, up to 128 clients
2.4 GHz 20/40 MHz channel widths
5 GHz 20/40/80/160 MHz channel widths
Ports 1× 2.5G WAN/LAN (PoE out 802.3at 15W → powers ODU), 3× GbE LAN, 1× RJ11 VoIP, 1× USB
NFC 13.56 MHz quick-pair (Android)
Other Easy Mesh, TR-069, VPN (IPSec / L2TP / PPTP), IPv4/IPv6, multiple APN
Power AC 100–240V in → DC 24V/1.0A
Physical 230×140.5×150 mm, 470 g, 0–40°C
FCC ID 2A5LO-ZLTW304VAPRO

Network Topology

       [ Cellular Tower / ISP ]
                  │
                  │ (5G / LTE / Fiber)
                  ▼
         ┌─────────────────┐
         │    ODU (Roof)   │
         │  Master Router  │
         │   192.168.0.1   │
         └────────┬────────┘
                  │
                  │ (Ethernet / PoE)
                  ▼
         ┌─────────────────┐
         │    IDU (Room)   │
         │  Slave Bridge   │
         │   169.254.0.2   │
         └────────┬────────┘
                  │
                  │ (Wi-Fi or LAN)
                  ▼
         ┌─────────────────┐
         │   YOUR LAPTOP   │
         │   192.168.0.x   │
         └─────────────────┘

Key insight: The IDU runs in bridge mode. Its management IP (169.254.0.2) is on a separate subnet from the LAN (192.168.0.x), so you need a secondary address on your machine to reach it (see §1.5).


Part 1 — IDU (ZLT W304VA PRO)

1.1 Serial Connection

  1. Open the back of the IDU and locate the UART/serial header.
  2. Connect serial wires to a USB-UART adapter.
  3. Connect the adapter to your machine and open a terminal:
    picocom -b 115200 /dev/ttyUSB0
    
  4. Verify the connection: press Enter and check for any response. Boot logs appearing is also confirmation.

1.2 Interrupt U-Boot Autoboot

The bootloader has a brief autoboot timer. You must catch it on reboot.

  1. Reboot the IDU (power cycle or Web UI).
  2. Watch for:
    Hit any key to stop autoboot
    
  3. Press any key immediately to drop into the U-Boot shell (ECNT> prompt).
  4. Authenticate with the known default credentials:
    • Username: telecomadmin
    • Password: nE7jA%5m

Verify U-Boot version if needed:

ECNT> version
U-Boot 2014.04-rc1 (Aug 18 2025 - 16:34:27)

1.3 Boot into Root Shell

From the ECNT> prompt, override the boot arguments to start /bin/sh instead of the normal init:

setenv verify no ; setenv console "ttyS0,115200n8 earlycon init=/bin/sh" ; flash imgread 2048 ; bootm

After the kernel loads, you'll land at a # root shell prompt.


1.4 Stabilize (Prevent Watchdog Reboot)

Because we bypassed normal init, the watchdog will trigger a reboot if essential services aren't started. Run these two commands quickly after getting the shell:

mount -t proc proc /proc ; mount -t tmpfs tmpfs /tmp
/usr/etc/init.d/rcS

Why: /etc/inittab defines rcS as the sysinit entry — it's the full initialization sequence the router runs on normal boot. Running it manually brings the system to a stable state.

::sysinit:/usr/etc/init.d/rcS
::askfirst:/sbin/getty -L ttyS0 115200 vt100

If reboots still occur, re-run both commands faster after the next root shell drop.


1.5 Network Access to IDU

The IDU's management interface is on a separate subnet:

# ip route
127.0.0.0/16 dev lo  scope link
169.254.0.0/16 dev br0  proto kernel  scope link  src 169.254.0.2

Add a secondary IP on your machine to reach it:

# Linux
ip addr add 169.254.0.100/16 dev <IF>

# macOS
sudo ifconfig <IF> alias 169.254.0.100 255.255.0.0

Verify: ping 169.254.0.2


1.6 Temporary Remote Shell (telnetd)

While still in the serial shell, start a telnet daemon:

telnetd -l /bin/sh -p 9876

From your machine:

telnet 169.254.0.2 9876

This is not persistent — it won't survive a reboot.

Note: /bin/login segfaults on the IDU, which is why we pass -l /bin/sh directly. Login prompts silently fail without indicating wrong credentials.


1.7 Persistent Telnet via tcapi

The tcapi tool reads/writes the router's config database (requires rcS to have run first).

Read current account config:

tcapi show Account

Relevant excerpt:

OID [196:1][TelnetEntry]:
    [Active = No]
    [telnet_username = admin]
    [telnet_passwd = 1234]
    [telnet_port = 23]

OID [195:1][Entry]:
    [username = telecomadmin]
    [web_passwd = nE7jA%5m]

OID [195:2][Entry]:
    [username = useradmin]
    [web_passwd = 1234]

OID [205:1][ConsoleEntry]:
    [console_username = gztzadmin]
    [console_passwd = 83583000]

Enable telnet and persist:

tcapi set Account_TelnetEntry Active Yes
tcapi save
reboot

After reboot, connect with the credentials from TelnetEntry:

telnet 169.254.0.2 23
# username: admin / password: 1234

Tight-window tip: If reboots happen before you can stabilize, prioritize: read credentials → set Active=Yes → save — all within the available window.


Part 2 — ODU (ZLT X17M)

Access to the ODU is achieved by pivoting through the IDU shell.

2.1 IDU–ODU IPC Mechanism

The IDU runs tz_mgr (management daemon) and the ODU runs configtools (management daemon). They communicate over a proprietary raw-Ethernet management plane using EtherTypes 0x9886/0x9887, exchanging config, commands, telemetry, and ACKs — no cryptographic authentication, only a plaintext checksum. See analysis/tz_mgr.md for a deeper analysis of tz_mgr; configtools is unanalyzed.

Shell commands can be injected from the IDU via a special IPC file:

File Purpose
/tmp/.tz_client_send_shell_flag Write a shell command here to send it to ODU
/tmp/tz_server_recv_shell_result ODU returns the exit code here

Test:

printf 'exit 0' > /tmp/.tz_client_send_shell_flag
cat /tmp/tz_server_recv_shell_result   # → 0

printf 'exit 1' > /tmp/.tz_client_send_shell_flag
cat /tmp/tz_server_recv_shell_result   # → 256

2.2 Output Exfiltration via Web Server

There's no direct way to read command stdout through the IPC channel. Workaround: redirect output to a file served by the ODU's web server (https://192.168.0.1).

The web root on both units is /tzwww.

Helper function (run on IDU):

send_cmd() {
    printf '%s > /tzwww/o.txt 2> /tzwww/e.txt; echo $? > /tzwww/rc.txt' "$*" \
        > /tmp/.tz_client_send_shell_flag
}

Usage:

send_cmd ls -lha
# then fetch https://192.168.0.1/o.txt  → stdout
# then fetch https://192.168.0.1/e.txt  → stderr
# then fetch https://192.168.0.1/rc.txt → exit code

2.3 Upload Busybox to ODU

The ODU's busybox is extremely minimal — no wget, nc, curl, telnet, or socat. The only available file transfer tool is ftpget.

Determine ODU architecture:

send_cmd uname -a
# Linux OpenWrt 5.4.238 #0 SMP Mon Sep 8 03:41:38 2025 aarch64 GNU/Linux

Architecture: aarch64.

Get a static busybox binary (e.g. from github.com/shutingrz/busybox-static-binaries-fat).

Start an FTP server on your machine (from the directory containing the binary):

python -m pyftpdlib -p 21 -w

Download the binary to ODU via IDU:

send_cmd ftpget -v -P 21 192.168.0.26 /tmp/busybox busybox-aarch64-linux-gnu

Verify transfer:

send_cmd ls -lha /tmp/busybox
# -rw-r--r-- 1 root root 2.0M Jul 19 00:17 /tmp/busybox

2.4 Temporary Shell on ODU

send_cmd chmod +x /tmp/busybox
send_cmd /tmp/busybox telnetd -f -p 23 -l /bin/sh

From your machine:

telnet 192.168.0.1

Note: /bin/login works correctly on the ODU (unlike the IDU). If you want credential-gated access, use -l /bin/login and set a strong password for root or another user (admin) first.


2.5 ODU Config & Credential Discovery

Once you have an ODU shell, mdlcfg can dump and decode the running config.

Dump full config (some values are encoded):

mdlcfg -e > /tmp/config.txt

Decode a specific value:

mdlcfg -g SYS_SENIOR_LOGIN_NAME   # web UI root/senior username
mdlcfg -g SYS_SENIOR_LOGIN_PWD    # web UI root/senior password

Web UI — advanced features with root credentials: Logging into https://192.168.0.1 with the senior credentials unlocks features hidden from the default user account:

  • Band locking (restrict to specific LTE/NR bands)
  • Physical cell ID (PCI) lock
  • IP passthrough / bridge mode config
  • Disabling TR-069

AT commands via atcmd: The ODU exposes a CLI wrapper for sending AT commands directly to the modem:

atcmd AT+CGMI        # manufacturer info
atcmd AT+CGMM        # model number
atcmd AT+CIMI        # IMSI
atcmd AT+COPS?       # current operator
atcmd AT+ECSQ                    # extended signal quality (RSRP, RSRQ, SINR, etc.)

2.6 Persistent Shell on ODU

/tmp is volatile. Copy busybox to persistent storage first, then hook it into init:

From the ODU shell:

cp /tmp/busybox /home/root/busybox

Append to /etc/inittab:

::respawnlate:/home/root/busybox telnetd -f -p 23 -l /bin/sh

Current /etc/inittab for reference:

::sysinit:/etc/init.d/rcS S boot
::shutdown:/etc/init.d/rcS K shutdown
# ttyS0::respawnlate:/etc/tzscript/login.sh

respawnlate ensures the service starts after the network stack is up, so the telnet port binds correctly.

After reboot:

telnet 192.168.0.1   # persistent root shell on ODU

Warning: Filesystem changes on the ODU persist through a factory reset — clean up after yourself.

Note: Factory reset may revert Wi-Fi SSIDs from ISP-configured values back to ZLT defaults.


Links


Disclaimer

This document is for educational and security research purposes only. All testing was performed on equipment owned by the author. Do not attempt these techniques on any device or network you do not own or have explicit written authorization to test. The author assumes no liability for misuse of the information contained herein.

About

Root shell access research on ZLT FWA equipment — W304VA PRO (IDU) & X17M (ODU), including binary analysis of the IDU/ODU management plane.

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages