You are here: Home » Wireless Attacks » mdk4

mdk4

mdk4 Description

MDK is a proof-of-concept tool to exploit common IEEE 802.11 protocol weaknesses.

MDK4 is a new version of MDK3.

MDK4 is a Wi-Fi testing tool from E7mer of 360PegasusTeam, ASPj of k2wrlz, it uses the osdep library from the aircrack-ng project to inject frames on several operating systems.

Features

  • Supports two WiFi card (one for receiving data, another for injecting data).
  • Supports block the specified ESSID/BSSID/Station MAC in command option.
  • Supports both 2.4 to 5GHz (Linux).
  • Supports IDS Evasion (Ghosting, Fragmenting, Does not fully work with every driver).
  • Supports packet fuzz testing.

Homepage: https://github.com/aircrack-ng/mdk4

Author: E7mer

License: GPLv3

mdk4 Help

MDK USAGE:

mdk4 <interface> <attack_mode> [attack_options]
mdk4 <interface in> <interface out> <attack_mode> [attack_options]

There are 9 attack modules, they are denoted by a single letter.

ATTACK MODE b: Beacon Flooding

Sends beacon frames to show fake APs at clients. This can sometimes crash network scanners and even drivers!

ATTACK MODE a: Authentication Denial-Of-Service

Sends authentication frames to all APs found in range. Too many clients can freeze or reset several APs.

ATTACK MODE p: SSID Probing and Bruteforcing

Probes APs and checks for answer, useful for checking if SSID has been correctly decloaked and if AP is in your sending range. Bruteforcing of hidden SSIDs with or without a wordlist is also available.

ATTACK MODE d: Deauthentication and Disassociation

Sends deauthentication and disassociation packets to stations based on data traffic to disconnect all clients from an AP.

ATTACK MODE m: Michael Countermeasures Exploitation

Sends random packets or re-injects duplicates on another QoS queue to provoke Michael Countermeasures on TKIP APs. AP will then shutdown for a whole minute, making this an effective DoS.

ATTACK MODE e: EAPOL Start and Logoff Packet Injection

Floods an AP with EAPOL Start frames to keep it busy with fake sessions and thus disables it to handle any legitimate clients. Or logs off clients by injecting fake EAPOL Logoff messages.

ATTACK MODE s: Attacks for IEEE 802.11s mesh networks

Various attacks on link management and routing in mesh networks. Flood neighbors and routes, create black holes and divert traffic! 

ATTACK MODE w: WIDS Confusion

Confuse/Abuse Intrusion Detection and Prevention Systems by cross-connecting clients to multiple WDS nodes or fake rogue APs.

ATTACK MODE f: Packet Fuzzer

A simple packet fuzzer with multiple packet sources and a nice set of modifiers. Be careful!

FULL OPTIONS:

ATTACK MODE b: Beacon Flooding
  Sends beacon frames to generate fake APs at clients.
  This can sometimes crash network scanners and drivers!
      -n <ssid>
         Use SSID <ssid> instead of randomly generated ones
      -a
         Use also non-printable caracters in generated SSIDs
         and create SSIDs that break the 32-byte limit
      -f <filename>
         Read SSIDs from file
      -v <filename>
         Read MACs and SSIDs from file. See example file!
      -t <adhoc>
         -t 1 = Create only Ad-Hoc network
         -t 0 = Create only Managed (AP) networks
         without this option, both types are generated
      -w <encryptions>
         Select which type of encryption the fake networks shall have
         Valid options: n = No Encryption, w = WEP, t = TKIP (WPA), a = AES (WPA2)
         You can select multiple types, i.e. "-w wta" will only create WEP and WPA networks
      -b <bitrate>
         Select if 11 Mbit (b) or 54 MBit (g) networks are created
         Without this option, both types will be used.
      -m
         Use valid accesspoint MAC from built-in OUI database
      -h
         Hop to channel where network is spoofed
         This is more effective with some devices/drivers
         But it reduces packet rate due to channel hopping.
      -c <chan>
         Create fake networks on channel <chan>. If you want your card to
         hop on this channel, you have to set -h option, too.
      -i <HEX>
         Add user-defined IE(s) in hexadecimal at the end of the tagged parameters
      -s <pps>
         Set speed in packets per second (Default: 50)

ATTACK MODE a: Authentication Denial-Of-Service
  Sends authentication frames to all APs found in range.
  Too many clients can freeze or reset several APs.
      -a <ap_mac>
         Only test the specified AP
      -m
         Use valid client MAC from built-in OUI database
      -i <ap_mac>
         Perform intelligent test on AP
         This test connects clients to the AP and reinjects sniffed data to keep them alive.
      -s <pps>
         Set speed in packets per second (Default: unlimited)

ATTACK MODE p: SSID Probing and Bruteforcing
  Probes APs and checks for answer, useful for checking if SSID has
  been correctly decloaked and if AP is in your sending range.
  Bruteforcing of hidden SSIDs with or without a wordlist is also available.
      -e <ssid>
         SSID to probe for
      -f <filename>
         Read SSIDs from file for bruteforcing hidden SSIDs
      -t <bssid>
         Set MAC address of target AP
      -s <pps>
         Set speed (Default: 400)
      -b <character sets>
         Use full Bruteforce mode (recommended for short SSIDs only!)
         You can select multiple character sets at once:
         * n (Numbers:   0-9)
         * u (Uppercase: A-Z)
         * l (Lowercase: a-z)
         * s (Symbols: ASCII)
      -p <word>
         Continue bruteforcing, starting at <word>.
      -r <channel>
         Probe request tests (mod-musket)

ATTACK MODE d: Deauthentication and Disassociation
  Sends deauthentication and disassociation packets to stations
  based on data traffic to disconnect all clients from an AP.
      -w <filename>
         Read file containing MACs not to care about (Whitelist mode)
      -b <filename>
         Read file containing MACs to run test on (Blacklist Mode)
      -s <pps>
         Set speed in packets per second (Default: unlimited)
      -x
         Enable full IDS stealth by matching all Sequence Numbers
         Packets will only be sent with clients' addresses
      -c [chan,chan,...,chan[:speed]]
         Enable channel hopping. When -c h is given, mdk4 will hop an all
         14 b/g channels. Channel will be changed every 3 seconds,
         if speed is not specified. Speed value is in milliseconds!
      -E <AP ESSID>
         Specify an AP ESSID to attack.
      -B <AP BSSID>
         Specify an AP BSSID to attack.
      -S <Station MAC address>
         Specify a station MAC address to attack.

ATTACK MODE m: Michael Countermeasures Exploitation
  Sends random packets or re-injects duplicates on another QoS queue
  to provoke Michael Countermeasures on TKIP APs.
  AP will then shutdown for a whole minute, making this an effective DoS.
      -t <bssid>
         Set target AP, that runs TKIP encryption
      -j
         Use the new QoS exploit which only needs to reinject a few packets instead
         of the random packet injection, which is unreliable but works without QoS.
      -s <pps>
         Set speed in packets per second (Default: 400)
      -w <seconds>
         Wait <seconds> between each random packet burst (Default: 10)
      -n <count>
         Send <count> random packets per burst (Default: 70)

ATTACK MODE e: EAPOL Start and Logoff Packet Injection
  Floods an AP with EAPOL Start frames to keep it busy with fake sessions
  and thus disables it to handle any legitimate clients.
  Or logs off clients by injecting fake EAPOL Logoff messages.
      -t <bssid>
         Set target WPA AP
      -s <pps>
         Set speed in packets per second (Default: 400)
      -l
         Use Logoff messages to kick clients

ATTACK MODE s: Attacks for IEEE 802.11s mesh networks
  Various attacks on link management and routing in mesh networks.
  Flood neighbors and routes, create black holes and divert traffic!
      -f <type>
         Basic fuzzing tests. Picks up Action and Beacon frames from the air, modifies and replays them:
         The following modification types are implemented:
         1: Replay identical frame until new one arrives (duplicate flooding)
         2: Change Source and BSSID (possibly resulting in Neighbor Flooding)
         3: Cut packet short, leave 802.11 header intact (find buffer errors)
         4: Shotgun mode, randomly overwriting bytes after header (find bugs)
         5: Skript-kid's automated attack trying all of the above randomly 🙂
      -b <impersonated_meshpoint>
         Create a Blackhole, using the impersonated_meshpoint's MAC address
         mdk4 will answer every incoming Route Request with a perfect route over the impersonated node.
      -p <impersonated_meshpoint>
         Path Request Flooding using the impersonated_meshpoint's address
         Adjust the speed switch (-s) for maximum profit!
      -l
         Just create loops on every route found by modifying Path Replies
      -s <pps>
         Set speed in packets per second (Default: 100)
      -n <meshID>
         Target this mesh network

ATTACK MODE w: WIDS Confusion
  Confuse/Abuse Intrusion Detection and Prevention Systems by
  cross-connecting clients to multiple WDS nodes or fake rogue APs.
  Confuses a WDS with multi-authenticated clients which messes up routing tables
      -e <SSID>
         SSID of target WDS network
      -c [chan,chan,...,chan[:speed]]
         Enable channel hopping. When -c h is given, mdk4 will hop an all
         14 b/g channels. Channel will be changed every 3 seconds,
         if speed is not specified. Speed value is in milliseconds!
      -z
         activate Zero_Chaos' WIDS exploit
         (authenticates clients from a WDS to foreign APs to make WIDS go nuts)
      -s <pps>
         Set speed in packets per second (Default: 100)

ATTACK MODE f: Packet Fuzzer
  A simple packet fuzzer with multiple packet sources
  and a nice set of modifiers. Be careful!
  mdk4 randomly selects the given sources and one or multiple modifiers.
      -s <sources>
         Specify one or more of the following packet sources:
         a - Sniff packets from the air
         b - Create valid beacon frames with random SSIDs and properties
         c - Create CTS frames to broadcast (you can also use this for a CTS DoS)
         p - Create broadcast probe requests
      -m <modifiers>
         Select at least one of the modifiers here:
         n - No modifier, do not modify packets
         b - Set destination address to broadcast
         m - Set source address to broadcast
         s - Shotgun: randomly overwrites a couple of bytes
         t - append random bytes (creates broken tagged parameters in beacons/probes)
         c - Cut packets short, preferably somewhere in headers or tags
         d - Insert random values in Duration and Flags fields
      -c [chan,chan,...,chan[:speed]]
         Enable channel hopping. When -c h is given, mdk4 will hop an all
         14 b/g channels. Channel will be changed every 3 seconds,
         if speed is not specified. Speed value is in milliseconds!
      -p <pps>
         Set speed in packets per second (Default: 250)

This version supports IDS Evasion (Ghosting). Just append --ghost <period>,<max_rate>,<min_txpower> after your attack mode identifier to enable ghosting!

<period>      : How often (in ms) to switch rate/power
<max_rate>    : Maximum Bitrate to use in MBit
<min_txpower> : Minimum TX power in dBm to use

NOTE: Does not fully work with every driver, YMMV…

This version supports IDS Evasion (Fragmenting). Just append --frag <min_frags>,<max_frags>,<percent> after your attack mode identifier to fragment all outgoing packets, possibly avoiding lots of IDS!

<min_frags> : Minimum fragments to split packets into
<max_frags> : Maximum amount of fragments to create
<percent>   : Percantage of packets to fragment

NOTE: May not fully work with every driver, YMMV…

HINT: Set max_frags to 0 to enable standard compliance

Solving the problem with an error «ioctl(SIOCSIWMODE) failed: Device or resource busy»

If you received a message when launching an attack:

ioctl(SIOCSIWMODE) failed: Device or resource busy
ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
sure RFMON is enabled: run 'airmon-ng start wlo1 <#>'
Sysfs injection support was not found either.
open interface wlo1 failed.
Starting OSDEP failed

This means that you need to stop programs that can use the wireless interface, and also put your wireless adapter into monitor mode.

To stop interfering processes:

sudo systemctl stop NetworkManager.service
sudo airmon-ng check kill

To switch to monitor mode, use the following commands:

sudo ip link set <INTERFACE> down
sudo iw <INTERFACE> set monitor control
sudo ip link set <INTERFACE> up

For example, to put the wlo1 interface into monitor mode:

sudo ip link set wlo1 down
sudo iw wlo1 set monitor control
sudo ip link set wlo1 up

mdk4 Usage Example

The ‘Beacon Flooding’ attack (b) (creates the appearance of the presence of many fake access points) on the wireless interface (wlo1), while also using non-printable characters in the generated SSID and creating SSIDs that break the 32-byte limit (-a) with valid MAC access points from the embedded OUI database (-m) and send packets at a speed of 500 packets per second (-s 500):

sudo mdk4 wlo1 b -a -m -s 500

How to install mdk4

Installation on Kali Linux

sudo apt install mdk4

Installation on BlackArch

sudo pacman -S pkg-config libnl libpcap
git clone https://github.com/aircrack-ng/mdk4
cd mdk4/
make
sudo make install

Installation on Linux (Debian, Mint, Ubuntu)

sudo apt install pkg-config libnl-3-dev libnl-genl-3-dev libpcap-dev
git clone https://github.com/aircrack-ng/mdk4
cd mdk4/
make
sudo make install

mdk4 Screenshots

The result of the b attack:

mdk4 Tutorials

For more information about how attacks work, see the mdk3 help.

Related tools

Also recommended: