Repository navigation
_port_ doesn't seem to convert to a port when passing in a port list #47
Description
Activity
Also can't reproduce on latest master:
➜ Interlace git:(master) interlace -t localhost -p 12 -c "nikto -h _target_:_port_" ===================================================== Interlace v1.5.2 by Michael Skelton (@codingo_) & Sajeeb Lohani (@sml555_) ===================================================== [17:09:55] [THREAD] [nikto -h localhost:12] Added to Queue 0%| | 0/1 [00:00<?, ?it/s]- Nikto v2.1.6 100%|██████████| 1/1 [00:00<00:00, 8.39it/s]Actualy, I've tested with pL, port list, and it does appear broken there. Updating issue:
➜ Interlace git:(master) interlace -t localhost -pL /tmp/ports.txt -c "nikto -h _target_:_port_" ===================================================== Interlace v1.5.2 by Michael Skelton (@codingo_) & Sajeeb Lohani (@sml555_) ===================================================== [17:10:32] [THREAD] [nikto -h localhost:_port_] Added to Queue 0%| | 0/1 [00:00<?, ?it/s]- Nikto v2.1.6 100%|██████████| 1/1 [00:00<00:00, 14.64it/s]- changed the title
[-]_port_ doesn't seem to convert to an actual port number[/-][+]_port_ doesn't seem to convert to a port when passing in a port list[/+]on Jun 6, 2019 The command I am having problems with is:
interlace -tL targets.txt -o /root/outputfolderhere/ -cL commands.txt -p 443I was not able to reproduce the issue with the following config:
Output:interlace -tL targets.txt -cL commands.txt -p 443 ================================================================================= Interlace v1.5.1 by Michael Skelton (@codingo_) & Sajeeb Lohani (@sml555_) ================================================================================= [08:40:59] [THREAD] [echo 128.0.0.1:443] Added to Queue [08:40:59] [THREAD] [echo 127.0.0.1:443] Added to Queue [08:40:59] [THREAD] [echo 127.0.0.1123:443] Added to Queue [08:40:59] [THREAD] [echo 128.0.0.1123:443] Added to Queue 128.0.0.1:443 127.0.0.1123:443 127.0.0.1:443 128.0.0.1123:443 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [00:00<00:00, 30.16it/s]targets.txt
127.0.0.1 128.0.0.1commands.txt
echo _target_:_port_ echo _target_123:_port_If you could provide the list of commands and targets that trigger this bug, it would be appreciated.
When adding nmap to the list without the port variable it breaks the port variable for nikto and sslscan.
nikto --host target:port >> output/target-nikto.txt
sslscan target:port >> output/target-sslscan.txt
nmap -sV --script=http-methods target >> output/target-nmap.txtThank-you for the extra detail @Ready-Hacker-One. @prodigysml and I are discussing this and will look into it shortly.
- added a commit that references this issue
on Jun 11, 2019

I ran the script with the settings as described to use nikto and have this error, it seems to not be converting port into the port number;