Skip to content

_port_ doesn't seem to convert to a port when passing in a port list #47

Description

@mrpaulstone

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;

  • Nikto v2.1.6


  • 0 host(s) tested

Activity

  1. self-assigned this
    on Jun 6, 2019
  2. prodigysml commented on Jun 6, 2019

    @prodigysml
    Collaborator

    Seems to be working fine for me.
    image

    Can we please get some more details of the exact command being run and OS details, python details, etc.?

    If at all possible, please test this command out too and post the output:
    interlace -t localhost -p 12 -c "nikto -h _target_:_port_"

    Thanks for using interlace!

  3. codingo commented on Jun 6, 2019

    @codingo
    Owner

    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]
    
  4. codingo commented on Jun 6, 2019

    @codingo
    Owner

    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]
    
  5. 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
  6. mrpaulstone commented on Jun 6, 2019

    @mrpaulstone
    Author

    The command I am having problems with is:
    interlace -tL targets.txt -o /root/outputfolderhere/ -cL commands.txt -p 443

  7. prodigysml commented on Jun 6, 2019

    @prodigysml
    Collaborator

    I 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.1
    

    commands.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.

  8. Ready-Hacker-One commented on Jun 10, 2019

    @Ready-Hacker-One

    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.txt

  9. codingo commented on Jun 10, 2019

    @codingo
    Owner

    Thank-you for the extra detail @Ready-Hacker-One. @prodigysml and I are discussing this and will look into it shortly.

  10. added a commit that references this issue on Jun 11, 2019
    552cdcf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions