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 22:09:10 -0600

One other comment/question: instead of using the default username iterator,
is there a list of common LPAR names that we can iterate over? Is the LPAR
name like a hostname, so that we can we begin with any discovered hostnames?

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/

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

Current thread: