Encrypted Hilink Uimage Firmware Header -

strings u-boot.bin | grep -i "aes" Look for key arrays in rodata section.

If you’ve ever run binwalk on a HiLink firmware update (e.g., from an E3372, B310, or AR series router) and seen only high entropy data with no recognizable UImage magic ( 0x27051956 ), you’ve likely encountered this encrypted header.

# Extract first 64+ bytes of encrypted header (adjust count) dd if=firmware.bin of=enc_header.bin bs=1 count=4096 openssl enc -aes-128-cbc -d -K $KEY -iv $IV -in enc_header.bin -out dec_header.bin Verify magic hexdump -C dec_header.bin | head -1 Should see 56 19 05 27 encrypted hilink uimage firmware header

magic = struct.unpack(">I", dec_header[0:4])[0] if magic == 0x27051956: print("Decryption successful") with open("dec_header.bin", "wb") as out: out.write(dec_header) The encrypted HiLink UImage header is a modest but effective speed bump against casual analysis. For a determined reverse engineer, it adds a few hours of work—identifying the key source, decrypting, and repacking. However, modern per-device keys and additional signature checks make widespread third-party firmware creation impractical.

If the magic appears, you have the correct key. The rest of the firmware may be encrypted in blocks. Many HiLink images encrypt only the header + first block. The remaining data may be plain or compressed. After decryption, run: strings u-boot

binwalk -E firmware.bin If the first 1 MB shows high entropy (>0.98) with no known signatures, suspect encryption.

Key for E3372 (v1): 0x4A,0x6F,0x6B,0x65,0x72,0x73,0x43,0x6F,0x6D,0x65,0x74,0x21,0x2A,0x2A,0x2A,0x00 Key for B310: Derived from serial number + static seed : Modern HiLink devices (2020+) use device-unique keys, making extraction harder but not impossible via hardware glitching. 3.3 Header Structure After Decryption Once decrypted, the header reverts to a standard UImage header with one twist: the ih_name field often contains a secondary signature or a plaintext marker like "SECURE_HILINK_V1" . For a determined reverse engineer, it adds a

Check for HiLink markers:

with open("firmware.bin", "rb") as f: enc_header = f.read(4096)

1. Introduction Huawei’s HiLink protocol powers millions of routers, LTE dongles, and IoT gateways. While standard U-Boot images (UImages) use a well-documented header structure ( struct image_header ), recent HiLink firmware variants employ an encrypted header layer —a deliberate obfuscation to prevent third-party firmware modifications, analysis, and repacking.

cipher = AES.new(key, AES.MODE_CBC, iv) dec_header = cipher.decrypt(enc_header)