Legion is an open source, easy-to-use, super-extensible and semi-automated network penetration testing tool that aids in discovery, reconnaissance and exploitation of information systems.
GNU General Public License v3.0
1.03k
stars
171
forks
source link
Interacting with host IP after the host has gone down causes lists to depopulate #77
Right-clicking on the IP Address under the host tab and requesting a re-scan or port scan, after the host has been powered off, causes the right-hand tabs (services, scripts, nikto, etc) to depopulate. The host IP also disappears from the host tab.
Note: this issue only seems to occur when attempting to interact with a host that has already been scanned or is in the process of being scanned; simply requesting a scan of a host that is down does not appear to have this effect. The issue occurs on both Kali and Parrot OS, both virtual machines running on VirtualBox. The hosts scanned were also virtual machines running on VirtualBox, specifically the Windows and Linux variants of Metasploitable3.
(before requesting a port scan)
(after requesting a port scan)
The above screenshots are both from a scan of the Linux version of Metasploitable.
The only tab that remains populated is the tools tab:
Requesting an nmap scan under the above conditions has the potential to cause Legion to crash, but only when specific actions are taken. Navigating to the Tools tab after either requesting a fast or full TCP scan (the other nmap scripts/scans don't seem to cause this, although I didn't check every single one) and right-clicking on any of the selections in the Host, Port column will cause legion to quit unexpectedly. The error message is as follows:
Right-clicking on the IP Address under the host tab and requesting a re-scan or port scan, after the host has been powered off, causes the right-hand tabs (services, scripts, nikto, etc) to depopulate. The host IP also disappears from the host tab.
Note: this issue only seems to occur when attempting to interact with a host that has already been scanned or is in the process of being scanned; simply requesting a scan of a host that is down does not appear to have this effect. The issue occurs on both Kali and Parrot OS, both virtual machines running on VirtualBox. The hosts scanned were also virtual machines running on VirtualBox, specifically the Windows and Linux variants of Metasploitable3.
(before requesting a port scan)
(after requesting a port scan)
The above screenshots are both from a scan of the Linux version of Metasploitable.
The only tab that remains populated is the tools tab:
Requesting an nmap scan under the above conditions has the potential to cause Legion to crash, but only when specific actions are taken. Navigating to the Tools tab after either requesting a fast or full TCP scan (the other nmap scripts/scans don't seem to cause this, although I didn't check every single one) and right-clicking on any of the selections in the Host, Port column will cause legion to quit unexpectedly. The error message is as follows: