Add mdns poisoning lab - cybersecurity #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
The network scenario name and topic
mDNS Poisoning - Cybersecurity
The network scenario description
This scenario has a server exposing a samba share and a victim trying to connect to it using user
valerio
. Both the victim and the server deploy an mDNS service to mimick a real life scenario that can be found in Active Directory environments.avahi-daemon
is a service that grants mDNS capabilities to Linux machinessmbd
andnmbd
are services deployed onserver1
to serveshare
, which is a samba share that requires a NetNTLMv2 authentication, equally to smb shares on Windowsvictim1
tries to connect toserver1
, with a typo in the machine name (not required for Windows environments)The attacker (
attacker1
) has a cybersecurity tool called responder in/root/responder/Responder.py
which allows the user to poison the network with LLMNR, NBT-NS and mDNS responses in order to redirect floating traffic to itself, notably including authentication attempts.The steps to test the network scenario
attacker1
python3 /root/responder/Responder.py -I eth0
and wait around 5 seconds