Recently I was asked to reset root password on some long forgotten Debian box. It was an easy and straightforward task, but, as there are some interesting pitfalls, I will describe the whole process of acquiring root shell without password using single-user mode and a couple of ways to prevent it.
What is single-user mode?
To access root shell without password you need to have physical access to the machine. Then you can modify kernel parameters to boot system into single-user mode which is just a single superuser maintenance/recovery mode with all services disabled.
How to access single-user mode?
Default Debian configuration will require password before executing single-user mode and this is a standard behavior found in today's Linux distributions.
To boot into this mode you need to turn on computer, access GRUB menu and select Recovery mode entry.
In case the Recovery mode menu entry is not available, you need to perform five simple steps in order to modify kernel parameters list.
- Turn on computer.
- Access GRUB menu.
- Edit existing menu entry (use
singlekeyword (alternatively you can use
S) to the Linux kernel parameters list.
F10while still in edit mode to continue boot process.
How single-user mode is protected?
It is protected by using
sulogin utility which is invoked by init process when system goes into single-user mode. You can verify this behavior manually by opening
/etc/inittab file and looking for single-user runlevel definition.
$ cat /etc/inittab
[...] # What to do in single-user mode. ~~:S:wait:/sbin/sulogin [...]
You can change it to shell interpreter if you do not want to enter password.
[...] # What to do in single-user mode. ~~:S:wait:/bin/sh [...]
How to overcome the above protection?
You can modify default behavior and specify your own command run as
init process as long as you can define kernel parameters.
So, according to the above statement you can get around this protection mechanism and boot into single-user mode to access root shell without password by specifying
init option in the kernel parameters list.
How to protect against such attacks?
Disable boot from external devices and lock boot device to the used one. Password protect BIOS settings. It is a weak protection but an important one, as circumventing it will surely draw an attention.
Disable generation of recovery mode menu entries and lock down boot-loader to require authentication before accessing command line.
This way is suitable only for personal devices but complements the above-mentioned methods with very strong protection. Full disk encryption will surely prevent access to the configuration files.
Use this mode in case of emergency when you need to enter directly single-user mode without executing any other commands or startup scripts.
To start this mode use
emergency kernel option in the same way as the above ones.
Please note that emergency shell configuration is hard-coded and will use
sulogin utility. Download
sysvinit package source code if you want to modify it.
initmanual page (section 8)
inittabmanual page (section 5)
suloginmanual page (section 8)