(Still in development) This platform is the result of human engineering. AI was used solely for security audits.

romdump.net
romdump.net › Dump index › Synology DiskStation DS124

Synology DiskStation DS124 DSM 7.2.2-72806

pending review

uploaded by admin ·

SquashFS image · ubifs · redboot · 304.5 MiB

request takedown

About this dump

Source

Downloaded from Synology's public download server: DSM_DS124_72806.pat

Format and unpacking

  • Container: Synology signed 0xADBEEF archive — 0xADBEEF header magic, msgpack header + 64-byte Ed25519 signature, then entries (high-entropy, no filesystem magic before decryption).
  • Encryption: each entry is XChaCha20-Poly1305 secretstream (libsodium); per-entry key = crypto_kdf_derive_from_key(master_key, subkey_id, ctx) with subkey_id/ctx from the header.
  • Tool: synacktiv/synodecrypt via a local libsodium (ctypes) + msgpack shim.
  • Key (reverse-engineered): the key table is baked into the proprietary libsynocodesign.so. I extracted libsynocodesign.so.7 from usr/lib/ inside hda1.tgz of the plaintext DSM 7.0.1-42218 DS920+ .pat, then brute-force-recovered the keys by sliding a 32-byte window over the .so and testing against a real target: Ed25519 signing key 64faba48feec6c8a2484d2489a11418a0e980317a9cc6b392f1041925b293fe0 at .so offset 0x23830; XChaCha20 master key 078a7529a07a998cffadb87d7378993b7d9ccfa7171f5c47f150838a6a7caf61 at adjacent offset 0x23858. Keys are stable across DSM 7.x.

Verification

  • Ed25519 header signature verified OK against the recovered signing key.
  • All per-entry BLAKE2b checksums matched (synodecrypt warns on mismatch; none).
  • Output is a valid tar: VERSION productversion=7.2.2, build=72806, unique=synology_rtd1619b_ds124.
  • Contains zImage kernel, rd.bin ramdisk and hda1.tgz root filesystem.

Contents

  • zImage kernel, rd.bin ramdisk and hda1.tgz root filesystem.
  • Platform: Realtek RTD1619B (ARM Cortex-A55, 1-bay).
  • Uploaded the decrypted tar.

Credit

Method reference: afflicted.sh / tpbreak.

Technical fingerprint

SquashFS image · ubifs · redboot

entropy 7.94 bits/byte · analysed 256.0 MiB (the leading part of a larger file)

Mostly compressed. 89% is compressed or encrypted data; the structures below mark where the streams and filesystems start.

  • compressed or encrypted 89%
  • code or packed data 6%
  • text and tables 4%
  • padding or empty 1%

Structures by offset

OffsetStructureKind
0x0 tar File format
0x101 tar Filesystem
0x639200 xz Compression
0x643dc6 gzip Compression
0x90141e bzip2 Compression
0x3b282b7 zip Compression
0x7b05589 grub Bootloader
0xedc2403 u-boot Bootloader
0xedc7019 lzop Compression
0xedc7290 fat Filesystem
0xee71c80 redboot Bootloader
0xf9c017d ubi Filesystem
0xf9c0189 ubifs Filesystem
0xf9c03e2 xfs Filesystem
0xf9c1c5b btrfs Filesystem
0xf9c1c6b cramfs Filesystem
0xf9c1d38 f2fs Filesystem
0xf9c205d ntfs Filesystem
0xf9c20f8 romfs Filesystem
0xf9c2101 squashfs Filesystem

What's inside

FieldDetected information
File format tar
Bootloader redboot 0xee71c80grub 0x7b05589u-boot 0xedc2403
Filesystem btrfs 0xf9c1c5bcramfs 0xf9c1c6bf2fs 0xf9c1d38ntfs 0xf9c205dromfs 0xf9c20f8squashfs 0xf9c2101ubi 0xf9c017dubifs 0xf9c0189xfs 0xf9c03e2fat 0xedc7290tar 0x101
Compression lzop 0xedc7019bzip2 0x90141exz 0x639200zip 0x3b282b7gzip 0x643dc6
Archive members DiskCompatibilityDB.tar

Symbols

2 names from the symbol tables of 1 ELF/PE file and strings that are symbols (capped: there may be more). A name searches the site for it; an offset opens the hex viewer there.

NameKindOffset
kXCpOY string 0x10465f0
tz0qyS8 string 0x38de525