Nexmon is our C-based firmware patching framework for Broadcom/Cypress WiFi chips that enables you to write your own firmware patches, for example, to enable monitor mode with radiotap headers and frame injection.
Before we started to work on this repository, we developed patches for the Nexus 5 (with bcm4339 WiFi chip) in the bcm-public repository and those for the Raspberry Pi 3 (with bcm43438 WiFi chip) in the bcm-rpi3 repository. To remove the development overhead of maintaining multiple separate repositories, we decided to merge them in this repository and add support for some additional devices. In contrast to the former repositories, here, you can only build the firmware patch without drivers and kernels. The Raspberry Pi 3 makes an exception, as here it is always required to also build the driver.
Our software may damage your hardware and may void your hardware’s warranty! You use our tools at your own risk and responsibility! If you don't like these terms, don't use nexmon!
- Starting with commit 4f8697743dc46ffc37d87d960825367531baeef9 the brcmfmac driver for the RPi3 can now be used as a regular interface. You need to use nexutil to activate monitor mode (
nexutil -m2
for monitor mode with radiotap headers), which will automtically adjust the interface type. - Starting with commit 184480edd6696392aae5f818f305f244606f2d17 you can choose different monitor mode options using nexutil. Use
nexutil -m1
to activate monitor mode without radiotap headers,nexutil -m2
to activate it with radiotap headers. The numbers were chosen as non-Nexmon firmwares also support native monitor mode without radiotap headers by activating monitor mode withnexutil -m1
. - Starting with commit 1bcfdc95b4395c2e8bdd962791ae20c4ba602f5b we changed the nexutil interface. Instead of calling
nexutil -m true
to activate monitor mode, you should now writenexutil -m1
. To get the current monitor mode state executenexutil -m
instead ofnexutil -n
.
The following devices are currently supported by our nexmon firmware patch.
WiFi Chip | Firmware Version | Used in | Operating System | M | RT | I | FP | UC | CT |
---|---|---|---|---|---|---|---|---|---|
bcm4330 | 5_90_100_41_sta | Samsung Galaxy S2 | Cyanogenmod 13.0 | X | X | X | X | O | |
bcm4339 | 6_37_34_43 | Nexus 5 | Android 6 Stock | X | X | X | X | X | O |
bcm43438 | 7_45_41_26 | Raspberry Pi 3 | Raspbian 8 | X | X | X | X | X | O |
bcm4358 | 7_112_200_17_sta | Nexus 6P | Android 7 Stock | X | X | X | X | O | |
bcm4358 | 7_112_201_3_sta | Nexus 6P | Android 7.1.2 Stock | X | X | X | X | O |
- M = Monitor Mode
- RT = Monitor Mode with RadioTap headers
- I = Frame Injection
- FP = Flash Patching
- UC = Ucode Compression
- CT = c't Article Support (for consistend support, use our ct-artikel branch)
Build patches for bcm4330, bcm4339 and bcm4358 using a x86 computer running Linux (e.g. Ubuntu 16.04)
-
Install some dependencies:
sudo apt-get install git gawk qpdf adb
-
Only necessary for x86_64 systems, install i386 libs:
sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386
-
Clone our repository:
git clone https://github.com/seemoo-lab/nexmon.git
-
In the root directory of the repository:
cd nexmon
- Setup the build environment:
source setup_env.sh
- Compile some build tools and extract the ucode and flashpatches from the original firmware files:
make
- Setup the build environment:
-
Go to the patches folder of your target device (e.g. bcm4339 for the Nexus 5):
cd patches/bcm4339/6_37_34_43/nexmon/
- Compile a patched firmware:
make
- Generate a backup of your original firmware file:
make backup-firmware
- Install the patched firmware on your smartphone:
make install-firmware
(make sure your smartphone is connected to your machine beforehand)
- Compile a patched firmware:
- Install at least nexutil and libfakeioctl from our utilities. The easiest way to do this is by using this app: https://play.google.com/store/apps/details?id=de.tu_darmstadt.seemoo.nexmon. But you can also build it from the source by executing
make
in the utilties folder (Note: you will need the Android NDK properly installed for this). - Connect to your Android phone using the ADB tools:
adb shell
- Make sure you are not connected to an access point
- Use nexutil to enable monitor mode:
nexutil -m2
- At this point the monitor mode is active. There is no need to call airmon-ng.
- Important: Most tools need a Radiotap interface to work properly. libfakeioctl emulates this type of interface for you, therefore, use LD_PRELOAD to load this library when you call the favourite tool (e.g. tcpdump or airodump-ng):
LD_PRELOAD=libfakeioctl.so tcpdump -i wlan0
To be able to communicate with the firmware without root priviledges, we created a UDP interface accessible through the libnexio
, which is also used by nexutil
. You first have to prove to the firmware that you generally have root priviledges by setting a securtiy cookie. Then you can use it for UDP based connections. Your wlan0 interface also needs an IP address in the 192.168.222.0/24 range or you have to change the default nexutil broadcast-ip
:
- Set the IP address of the wlan0 interface:
ifconfig wlan0 192.168.222.1 netmask 255.255.255.0
- Set the security cookie as root:
nexutil -x<cookie (uint)>
- Start a UDP connection for example to activate monitor mode:
nexutil -X<cookie> -m1
- Make sure the following commands are executed as
root
- Upgrade your Raspbian installation:
apt-get update && apt-get upgrade
- Install the kernel headers to build the driver and some dependencies:
sudo apt install raspberrypi-kernel-headers git libgmp3-dev gawk
- Clone our repository:
git clone https://github.com/seemoo-lab/nexmon.git
- Go into the root directory of our repository:
cd nexmon
- Setup the build environment:
source setup_env.sh
- Compile some build tools and extract the ucode and flashpatches from the original firmware files:
make
- Setup the build environment:
- Go to the patches folder for the bcm43438 chipset:
cd patches/bcm43438/7_45_41_26/nexmon/
- Compile a patched firmware:
make
- Generate a backup of your original firmware file:
make backup-firmware
- Install the patched firmware on your RPI3:
make install-firmware
- Compile a patched firmware:
- Install nexutil: from the root directory of our repository switch to the nexutil folder:
cd utilities/nexutil/
. Compile and install nexutil:make && make install
. - Optional: remove wpa_supplicant for better control over the WiFi interface:
apt-get remove wpasupplicant
Our modified driver sets the interface in monitor mode as soon as the interface goes up:ifconfig wlan0 up
- In the default setting the brcmfmac driver can be used regularly as a WiFi station with out firmware. To activate monitor mode, execute
nexutil -m2
. - At this point the monitor mode is active. There is no need to call airmon-ng.
- The interface already set the Radiotap header, therefore, tools like tcpdump or airodump-ng can be used out of the box:
tcpdump -i wlan0
- Note: It is not possible to connect to an access point anymore using our modified driver and firmware, if you whant to go back to the default behaviour you will need to load the original driver and firmware.
The Wi-Fi firmware consists of a read-only part stored in the ROM of every Wi-Fi chip and another part that is loaded by the driver into the RAM. To analyze the whole firmware, one needs to extract the ROM. There are two options to do this. Either you write a firmware patch that simply copies the contents of the ROM to RAM and then you dump the RAM, or you directly dump the ROM after loading the regular firmware into the RAM. Even though, the second option is easier, it only works, if the ROM can be directly accessed by the driver, which is not always the case. Additionally, the firmware loaded into RAM can contain ROM patches that overlay the data stored in ROM. By dumping the ROM after loading the original RAM firmware, it contains flash patches. Hence, the ROM needs to be dumped again for every RAM firmware update to be consistent. As a conclusion, we prefer to dump the clean ROM after copying it to RAM.
To dump the ROM directly, you need to know, where to find it and how large it is. On chips with Cortex-M3 it is usually at upper addresses such as 0x800000, while on chips with Cortex-R4 it is likely at 0x0. Run dhdutil to perform the dump:
dhdutil membytes -r 0x0 0xA0000 > rom.bin
For the BCM4339 and BCM4358, we created rom_extraction
projects` that load a firmware patch that copies ROM to
RAM and them dumps it using dhdutil. To dump the ROM simply execute the following in the project directory:
make dump-rom
After ROM extraction, the rom.bin
file will be copies to the corresponding firmwares subdirectory. To apply the
flash patches of a specific RAM firmware version, enter its directory and execute:
make rom.bin
buildtools
: Contains compilers and other tools to build the firmwarefirmwares
<chip version>
<firmware version>
<firmware file>
: The original firmware that will be loaded into the RAM of the WiFi Chipdefinitions.mk
: Contains mainly firmware specific addressesstructs.h
: Structures only valid for this firmware versionMakefile
: Used to extract flashpatches and ucodeflashpatches.c
(generated by Makefile): Contains flashpatchesucode.bin
(extracted by Makefile): Contains uncompressed Ucode
structs.common.h
: Structures that are common between firmware versions
patches
<chip version>
<firmware version>
nexmon
Makefile
: Used to build the firmwarepatch.ld
: Linker filesrc
patch.c
: General patches to the firmwareinjection.c
: Code related to frame injectionmonitormode.c
: Code related to monitor mode with radiotap headersioctl.c
: Handling of custom IOCTLs- ...
obj
(generated by Makefile): Object files created from C fileslog
(generated by Makefile): Logs written during compilationgen
(generated by Makefile): Files generated during the build processnexmon.pre
(generated by gcc plugin): Extracted at-attributes and targetregion-pragmasnexmon.ld
(generated from nexmon.pre): Linker file use to place patch code at defined addresses in the firmwarenexmon.mk
(generated from nexmon.pre): Make file used take code from patch.elf and place it into firmwareflashpatches.ld
(generated from nexmon.pre): Linker file that places flashpatches at target locations in firmware ROMflashpatches.mk
(generated from nexmon.pre): Make file used to insert flashpatch config and data structures into firmwarepatch.elf
(generated from object files and linker scripts): contains the newly compiled code placed at predefined addresses
common
wrapper.c
: Wrappers for functions that already exist in the firmwareucode_compression.c
: tinflate based ucode decompressionradiotap.c
: RadioTap header parserhelper.c
: Helpful utility functions
include
: Common include filesfirmware_version.h
: Definitions of chip and firmware versionspatcher.h
: Macros use to perform patching for existing firmware code (e.g., BPatch patches a branch instruction)capabilities.h
: Allows to indicate capabilities (such as, monitor mode and frame injection)nexioctl.h
: Defines custom IOCTL numbers
- bcmon: Monitor Mode and Frame Injection for the bcm4329 and bcm4330
- monmob: Monitor Mode and Frame Injection for the bcm4325, bcm4329 and bcm4330
- imon: Penetration Testing for Apple devices with Broadcom WiFi Chip
If you know more projects that use nexmon, let us know and we will add a link.
- Project Zero: Over The Air: Exploiting Broadcom's Wi-Fi Stack (Part 1)
- Project Zero: Over The Air: Exploiting Broadcom's Wi-Fi Stack (Part 2)
- M. Schulz. Nexmon - Wie man die eigene WLAN-Firmware hackt, c't 26/2016, S. 168, Heise Verlag, 2016.
- M. Schulz, D. Wegemer, M. Hollick. DEMO: Using NexMon, the C-based WiFi firmware modification framework, Proceedings of the 9th ACM Conference on Security and Privacy in Wireless and Mobile Networks, WiSec 2016, July 2016.
- M. Schulz, D. Wegemer and M. Hollick. [NexMon: A Cookbook for Firmware Modifications on Smartphones to Enable Monitor Mode] (http://arxiv.org/abs/1601.07077), CoRR, vol. abs/1601.07077, December 2015. bibtex
- Matthias Schulz [email protected]
- Daniel Wegemer [email protected]