Nmap Development mailing list archives

Re: [NSE] Mainframe (z/OS & z/VM) Network Job Entry (NJE) Node Name Brute Forcer


From: Daniel Miller <bonsaiviking () gmail com>
Date: Mon, 2 Nov 2015 21:29:24 -0600

Phil,

Do you mind trying the revised script I attached? Mostly cosmetic changes,
but I want to make sure I didn't break something.

The NSEdoc for the brute library was broken before today, but now you can
see that there is a script-arg "brute.firstonly" that does what you want
regarding stopping after the first found credential.
https://nmap.org/nsedoc/lib/brute.html

Dan

On Fri, Sep 4, 2015 at 6:39 PM, Main Framed <mainframed767 () gmail com> wrote:

NJE relies on node names for initial client handshake.

This script attempts to brute force the node name of a target mainframe.
It will likely be the LPAR name but not always. It relies on nje-info.nse,
submitted previously (which identifies the port running NJE).

This is my first bruteforce script, I have others so let me know if
there's anything wrong with it or if there are things I should change.

One question I had, generally a system will only have one node name. Is
there a way to get Brute to quit after finding the first valid cred?


--
Soldier of Fortran
@mainframed767

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Attachment: nje-node-brute.nse
Description:

_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Current thread: