Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extra space is causing an invalid target in every scan result #66

Open
FiveOFive opened this issue Sep 8, 2020 · 0 comments
Open

Extra space is causing an invalid target in every scan result #66

FiveOFive opened this issue Sep 8, 2020 · 0 comments

Comments

@FiveOFive
Copy link

An extra space is causing an invalid target in every scan result.

Details to reproduce:
Run a scan such as the code below:

const opts = {
  range: ['scanme.nmap.org']
};

nmap.scan(opts, function(err, report) {
  console.log(JSON.stringify(report, null, 2));
});

The output, contains an invalid target entry with empty specification.

"target": [
  {
    "item": {
        "specification": "",
        "status": "skipped",
        "reason": "invalid"
      }
    }
]

And there are two spaces in the args between the ports and the host

"args": "nmap --host-timeout=120s -T4 -oX - -p1-1024  scanme.nmap.org",

I submitted a pull request to fix this - https://github.com/jas-/node-libnmap/pull/64
Thanks for the great library!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant