Skip to content

Latest commit

 

History

History
186 lines (105 loc) · 5.41 KB

T1040.md

File metadata and controls

186 lines (105 loc) · 5.41 KB
Raw

T1040 - Network Sniffing

Description from ATT&CK

Adversaries may sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.

Data captured via this technique may include user credentials, especially those sent over an insecure, unencrypted protocol. Techniques for name service resolution poisoning, such as LLMNR/NBT-NS Poisoning and SMB Relay, can also be used to capture credentials to websites, proxies, and internal systems by redirecting traffic to an adversary.

Network sniffing may also reveal configuration details, such as running services, version numbers, and other network characteristics (e.g. IP addresses, hostnames, VLAN IDs) necessary for subsequent Lateral Movement and/or Defense Evasion activities.

Atomic Tests


Atomic Test #1 - Packet Capture Linux

Perform a PCAP. Wireshark will be required for tshark. TCPdump may already be installed.

Upon successful execution, tshark or tcpdump will execute and capture 5 packets on interface ens33.

Supported Platforms: Linux

Inputs:

Name Description Type Default Value
interface Specify interface to perform PCAP on. String ens33

Attack Commands: Run with bash! Elevation Required (e.g. root or admin)

tcpdump -c 5 -nnni #{interface}
tshark -c 5 -i #{interface}

Dependencies: Run with bash!

Description: Check if at least one of the tools are installed on the machine.
Check Prereq Commands:
if [ ! -x "$(command -v tcpdump)" ] && [ ! -x "$(command -v tshark)" ]; then exit 1; else exit 0; fi;
Get Prereq Commands:
echo "Install tcpdump and/or tshark for the test to run."; exit 1;


Atomic Test #2 - Packet Capture macOS

Perform a PCAP on macOS. This will require Wireshark/tshark to be installed. TCPdump may already be installed.

Upon successful execution, tshark or tcpdump will execute and capture 5 packets on interface en0A.

Supported Platforms: macOS

Inputs:

Name Description Type Default Value
interface Specify interface to perform PCAP on. String en0A

Attack Commands: Run with bash! Elevation Required (e.g. root or admin)

sudo tcpdump -c 5 -nnni #{interface}    
if [ -x "$(command -v tshark)" ]; then sudo tshark -c 5 -i #{interface}; fi;

Dependencies: Run with bash!

Description: Check if at least one of the tools are installed on the machine.
Check Prereq Commands:
if [ ! -x "$(command -v tcpdump)" ] && [ ! -x "$(command -v tshark)" ]; then exit 1; else exit 0; fi;
Get Prereq Commands:
echo "Install tcpdump and/or tshark for the test to run."; exit 1;


Atomic Test #3 - Packet Capture Windows Command Prompt

Perform a packet capture using the windows command prompt. This will require a host that has Wireshark/Tshark installed.

Upon successful execution, tshark will execute and capture 5 packets on interface "Ethernet".

Supported Platforms: Windows

Inputs:

Name Description Type Default Value
interface Specify interface to perform PCAP on. String Ethernet
wireshark_url wireshark installer download URL url https://2.na.dl.wireshark.org/win64/Wireshark-win64-3.2.6.exe
tshark_path path to tshark.exe path c:\program files\wireshark\tshark.exe

Attack Commands: Run with command_prompt! Elevation Required (e.g. root or admin)

"c:\Program Files\Wireshark\tshark.exe" -i #{interface} -c 5

Dependencies: Run with powershell!

Description: tshark must be installed and in the default path of "c:\Program Files\Wireshark\Tshark.exe".
Check Prereq Commands:
if (test-path "#{tshark_path}") {exit 0} else {exit 1}
Get Prereq Commands:
Invoke-WebRequest -OutFile $env:temp\wireshark_installer.exe #{wireshark_url}
Start-Process $env:temp\wireshark_installer.exe /S


Atomic Test #4 - Windows Internal Packet Capture

Uses the built-in Windows packet capture After execution you should find a file named trace.etl and trace.cab in the temp directory

Supported Platforms: Windows

Attack Commands: Run with command_prompt! Elevation Required (e.g. root or admin)

netsh trace start capture=yes tracefile=%temp%\trace.etl maxsize=10

Cleanup Commands:

netsh trace stop
TIMEOUT /T 50
del %temp%\trace.etl
del %temp%\trace.cab