Finding the SqueezeBox Radio Default SSH Passwort

Note: This post was originally hosted somewhere else. Republishing here for better visibility. Also, the slimdevices wiki has a section on SSH authentication that mentions the default password. I must have missed it.


I have a SqueezeBox Radio at home. It does a nice job of playing music from the internet and my local network. The radio is clearly a linux device and it even listens on por 22. But I don't have the password and this always bummed me. I can stream music to the radio from my local network using the logitech media server software. When migrating server hardware, I looked around what to keep and noticed an updates folder in /var/lib/squeezeboxserver. It turns out, that when the radio asks for updates, the local server is in charge of getting the update file and providing it to the radio.

$ ls updates/
baby_7.7.3_r16676.bin  baby.version
$ ls -l updates/
-rw-r--r-- 1 freddy freddy 14771422 Sep  2 07:54 baby_7.7.3_r16676.bin
-rw-r--r-- 1 freddy freddy      139 Sep  2 07:53 baby.version
$ cat updates/baby.version
7.7.3 r16676 Fri Feb 14 09:25:26 PST 2014
Base build revision:  bad080aecfec8226a4c1699b29d32cbba4ba396b
$ file updates/*
updates/baby_7.7.3_r16676.bin: Zip archive data, at least v2.0 to extract
updates/baby.version:          ASCII text

So, not knowing this, I had the firmware information on my disk all along? It is on.

Understanding the Firmware Update

This turned out very simple and accessible. Thanks Logitech! Unzipping yields multiple files, among them text files with metadata a zImage (~2.8M) and root.cramfs (13M). Alright, let's mount the root filesystem and take a look around

$ mount -o loop root.cramfs /mnt/
$ cat /etc/shadow

Asking a search engine yields nothing, so we have to crack it ourselves. Running john on this takes less than a second.

The password is 1234

Logging in

Logging in is a bit harder than it seems. The radio uses ancient SSH, which offers outdated legacy ciphers:

ssh  192.168.x.y -l root
Unable to negotiate with 192.168.x.y port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

A quick search shows that we can re-enable the legacy crypto:

$ ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 192.168.x.y -l root
root@192.168.x.y's password:

This network device is for authorized use only. Unauthorized or improper use
of this system may result in you hearing very bad music. If you do not consent
to these terms, LOG OFF IMMEDIATELY.

Ha, only joking. Now you have logged in feel free to change your root password
using the 'passwd' command. You can safely modify any of the files on this
system. A factory reset (press and hold add on power on) will remove all your
modifications and revert to the installed firmware.


Other posts

  1. Help Test Firefox's built-in HTML Sanitizer to protect against UXSS bugs
  2. Remote Code Execution in Firefox beyond memory corruptions
  3. XSS in The Digital #ClimateStrike Widget
  4. Chrome switching the XSSAuditor to filter mode re-enables old attack
  5. Challenge Write-up: Subresource Integrity in Service Workers
  6. Finding the SqueezeBox Radio Default SSH Passwort
  7. New CSP directive to make Subresource Integrity mandatory (`require-sri-for`)
  8. Firefox OS apps and beyond
  9. Teacher's Pinboard Write-up
  10. A CDN that can not XSS you: Using Subresource Integrity
  11. The Twitter Gazebo
  12. German Firefox 1.0 ad (OCR)
  13. My thoughts on Tor appliances
  14. Subresource Integrity
  15. Revoke App Permissions on Firefox OS
  16. (Self) XSS at Mozilla's internal Phonebook
  17. Tales of Python's Encoding
  18. On the X-Frame-Options Security Header
  19. html2dom
  20. Security Review: HTML sanitizer in Thunderbird
  21. Week 29 2013
  22. The First Post