Embedded Framework and C-Based Toolchain Hardening
Limit BusyBox, embedded frameworks, and toolchains to only those libraries and functions being used when configuring firmware builds. Embedded Linux build systems such as Buildroot, Yocto and others typically perform this task. Removal of known insecure libraries and protocols such as Telnet not only minimize attack entry points in firmware builds, but also provide a secure-by-design approach to building software in efforts to thwart potential security threats.
Hardening a library Example: It is known that compression is insecure (amongst others),SSLv2 is insecure, SSLv3 is insecure, as well as early versions of TLS . In addition, suppose you don't use hardware and engines, and only allow static linking. Given the knowledge and specifications, you would configure the OpenSSL library as follows:
$ Configure darwin64-x86_64-cc -no-hw -no-engine -no-comp -no-shared -no-dso -no-ssl2 -no-ssl3 --openssldir=
Selecting one shell Example: Utilizing buildroot, the screenshot below demonstrates only one Shell being enabled, bash. (Note: Buildroot examples are shown below but there are other ways to accomplish the same configuration with other embedded Linux build systems.)
Hardening Services Example: The screenshot below shows openssh enabled but not FTP daemons proftpd and pure-ftpd. Only enable FTP if TLS is to be utilized. For example, proftpd and pureftpd require custom compilation to use TLS with mod_tls for proftpd and passing
./configure --with-tls for pureftpd.
Hardening Das U-boot Example: Often, physical access to an embedded device enables attack paths to modify bootloader configurations. Below, example best practice configurations for
uboot_config are provided. Note: The
uboot_config file is typically auto generated depending on the build environment and specific board.
Configure "Verified Boot" (secure boot) for U-Boot 2013.07 versions and above. Verified Boot is not enabled by default and requires board support with the below configurations required at the minimum.
CONFIG_ENABLE_VBOOT=y #Enables Verified Boot
CONFIG_FIT_SIGNATURE=y #Enables signature verification of FIT images.
CONFIG_RSA=y #Enables RSA algorithm used for FIT image verification
CONFIG_OF_SEPARATE=y #Enables separate build of u-Boot from the device tree.
CONFIG_FIT=y #Enables support for Flat Image Tree (FIT) uImage format.
CONFIG_OF_CONTROL=y #Enables Flattened Device Tree (FDT) configuration.
CONFIG_DEFAULT_DEVICE_TREE=y #Specifies the default Device Tree used for the run-time configuration of U-Boot.
Afterwards, a series of steps are needed for configuring Verified Boot. An example overview of building Verified Boot for a Beaglebone black board is:
- Build U-Boot for the board, with the verified boot options enabled.
- Obtain a suitable Linux kernel (preferably the latest)
- Create a Image Tree Source file (ITS) file describing how you want the kernel to be packaged, compressed and signed.
- Create an RSA key pair with RSA2048 and use SHA256 hashing algorithm for authentication (store your private key in a safe place and not hardcoded into firmware)
- Sign the kernel
- Put the public key into U-Boot's image
- Put U-Boot and the kernel onto the board
- Test the image and boot configurations
In addition to the above, make the applicable configurations valid to the context of your embedded device. Below are notable configurations that can be made.
CONFIG_BOOTDELAY -2. #Prevents access to u-boot's console when auto boot is used
CONFIG_CMD_USB=n #Disables basic USB support and the usb command
CONFIG_USB_UHCI: defines the lowlevel part.
CONFIG_USB_KEYBOARD: enables the USB Keyboard
CONFIG_USB_STORAGE: enables the USB storage devices
CONFIG_USB_HOST_ETHER: enables USB ethernet adapter support
Disabling serial console output in U-Boot via the following configuration macros:
To enable immutable U-boot environment variables to prevent unauthorized changes (e.g. Modifying bootargs, updating verified boot public keys etc.) or side-loading of firmware, remove non-volatile memory settings such as the following:
Considerations (Disclaimer: The List below is non-exhaustive):
- Ensure services such as SSH have a secure password created.
- Remove unused language interpreters such as: perl, python, lua.
- Remove dead code from unused library functions.
- Remove unused shell interpreters such as: ash, dash, zsh.
- Remove legacy insecure daemons which includes but not limited to:
Remove unused/unnecessary utilities such as:
- sed, wget, curl, awk, cut, df, dmesg, echo, fdisk, grep, mkdir, mount (vfat), printf, tail, tee, test (directory), test (file), head, cat
Automotive Grade Linux (AGL) has developed an example table of common utilities and their usage for debug or production environments (builds).
|Utility Name||Location||Debug Environment||Production Environment|
|Dropbear||Remove “dropbear” from ‘/etc/init.d/rcs’||EXCLUDE||EXCLUDE|
|Who and whoami||/bin/whoami||INCLUDE||EXCLUDE|
Utilize tools such as Lynis for hardening auditing and suggestions.
* wget --no-check-certificate https://github.com/CISOfy/lynis/archive/master.zip && unzip master.zip && cd lynis-master/ && bash lynis audit system
- Review the report in:
- Review the report in:
Perform iterative threat model exercises with developers as well as relative stakeholders on software running on the embedded device.
- http://isa99.isa.org/Public/Documents/ISA-62443-4-1-WD.pdf (page 34-38)
- https://events.linuxfoundation.org/sites/events/files/slides/belloni-petazzoni-buildroot-oe_0.pdf - Details on buildroot and yocto
- GNU C Library Vulnerability in Industrial Products
- Linux Exploit Quick Listing
- Hardened U-boot
- Improving Your Embedded Linux Security Posture with Yocto