Skip to content
Branch: master
Find file History
Latest commit 8f95dea Sep 11, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
internalblue
.gitignore
README.md
sample-nexmaster-galaxys9slave.pcapng

README.md

README

Requirements

  • Rooted Nexus 5 running the internalblue/android_bluetooth_stack/nexus5_android6_0_1/bluetooth.default.so Android Bluetooth stack

  • Laptop running a Linux based OS

  • Wireshark

Perform the KNOB attack

  1. Connect the Nexus 5 to your laptop via USB

  2. Configure and install our modified internalblue v0.1:

    • Open internalblue/internalblue/core.py and set NEXUS5_MODE according to the type of attack you want to perform. For example, set NEXUS5_MODE = MASTER_MITM if you want to use the Nexus 5 as the master device who initiates the negotiation.
    • Open a terminal, cd into internalblue, and run sudo python2 setup.py install
  3. Open a terminal and run internalblue

  4. From the internalblue prompt start LMP monitoring with monitor lmp start

    • A Wireshark window should pop up
    • If from the terminal you get a bunch of error messages including Error: unrecognized option -mthumb you should close the Wireshark window and internalblue, uncomment line 116 in internalblue/internalblue/core.py to trigger a custom exception, and restart from step 2 (installation).
  5. Pair a target Bluetooth device with the Nexus 5

  6. If you are performing the attack with the Nexus 5 as the master (NEXUS5_MODE = MASTER_MITM), then start a connection from the Nexus 5 to the target device. In other words the Nexus 5 has to be the master and should send the first LMP_encryption_key_size_req packet. If you are performing the attack with the Nexus 5 as the slave (NEXUS5_MODE = SLAVE_MITM), then start a connection from the other victim device.

  7. From Wireshark you should see the devices negotiating encryption keys with 1 byte of entropy (like what happens from packet 121 to packet 127 in our sample pcap file. Note that our sample pcap was captured before the release of any KNOB attack patch.

  8. Check if the target device is vulnerable

    • Android (tested only on a Pixel 2): If the target device sends first an LMP_accept (in response to an LMP_start_encryption_req) and then an LMP_detach message due to security reasons then the target device is patched against the KNOB attack.
  9. Close Wireshark and internalblue

FAQ

What should I do if I find a new vulnerable device

Please let us know, such as we can update our evaluation results.

Wait, this is not an attack over the air

We implemented the KNOB attack by simulating a remote attacker using InternalBlue. Alternatively, we could have conducted the attacks over the air using signal manipulation and (reactive) jamming. However, the InternalBlue setup is simpler, more reliable, cheaper, and easier to reproduce than the over-the-air setup, while affecting the victims in the same way as a remote over the air attack.

You can’t perform that action at this time.