Stops importing nmap import at 5% #175
Comments
|
Hi, when you import the nmap file into Legion, does it first import to 100%, populating Legion with services, and then get stuck at 5%? Just want to make sure I'm seeing the same result. |
|
Yup! It looks like it's stuck on some script output: |
|
just cloned today from github, I have the same issue. Update: seems to only hang when started with a clean slate. When importing into a current project, it straight up crashes (immediately). |
|
@securesean @MidnightSeer Mind giving it another try with 0.3.7? |
|
Hi, On Kali On Legion from Kali repos nmap -Pn -sSV -vvvv --script vulners .... -oX /root/nmap_scan.xml -T4 --open error msg import to already created session{"time": "2020-10-26 11:30:08,089", "name": "Importing nmap xml from /root/nmapscan.xml...", "level": "INFO", "data": {"logger_name": "legion"}, "context": {"module": "view", "filename": "view.py", "line": 485}} The above exception was the direct cause of the following exception: Traceback (most recent call last): error msg import to already created sessionsqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) UNIQUE constraint failed: nmapSessionObj.filename error msg import to new session{"time": "2020-10-26 11:32:18,140", "name": "Importing nmap xml from /root/nmap_scan.xml...", "level": "INFO", "data": {"logger_name": "legion"}, "context": {"module": "view", "filename": "view.py", "line": 485}} |
|
Confirmed that fix worked for me. @re8el I think it would be best if you openned a new issue and uploaded your 'nmap_scan.xml' files so the problem can be replicated and debugged (otherwise we don't know what you're scanning). Note: The best way to test with the latest/greatest legion is to use Docker. On Kali the best way to do this is: apt remove docker
apt install docker.io
git clone https://github.com/GoVanguard/legion
cd legion/docker
# add a folder to the docker container in runIt.sh so you can pull files in and out. In the docker run command I add: "-v /opt/legion_output:/opt/legion_output"
./runIt.shThen copy the xml scan into the /opt/legion_output folder and try to import it:
|
Hello! Legion keeps freezing when I import an XML vuln scan from nmap (XML file attached). The nmap xml file was produced by the command
nmap -sV --script vuln -oA blueVulnScan 10.10.10.40against hackthebox.eu'sblueWindows 7 Pro x64 machine that's vulnerable to the EternalBlue exploit. I used the natively installed version of legion on the rolling kali distro (LEGION 0.3.6-1580902879 late update 02/05/2020). I don't know if the latest version of legion fixed this bug. Each time I tried to natively install it from the git repo my Kali VM got bricked when I restarted services relying on the old dependencies. I also failed to get docker working on Kali (but that's a separate bug)blueVulnScan.zip
The text was updated successfully, but these errors were encountered: