Feature #2296

Adding RPORTS to scanner modules

Added by Thomas Ring over 1 year ago. Updated over 1 year ago.

Status:New Start date:07/24/2010
Priority:Normal Due date:
Assignee:Tod Beardsley % Done:

0%
Category:general
Target version:-
Resolution: How To Use:
Release Note:

Description

We have RHOSTS...why not RPORTS :)

This is more or less a proof of concept (there are other modules that could make use of this)...though it does work nicely as far as I can tell...

I had to separate the run into do_host from run_host so that if something bombed with a host/port combo (connection refused), I could either move on (by re-raising the exception) or skip the host (connection timeout, no route to host (there are probably others that should be here).

tnslsnr_version.rb - scanner/oracle/tnslsnr_version with RPORTS (4.1 kB) Thomas Ring, 07/24/2010 01:34 pm

tnslsnr_version.rb (3.2 kB) Thomas Ring, 07/26/2010 06:39 am

History

#1
Updated by Thomas Ring over 1 year ago

Bleh...lets try that again...

I could either move on by re-raising the exception (connection timeout, no route to host (there should probably be others here)) or by silently ignoring it so it tries next port (connection refused).

#2
Updated by Thomas Ring over 1 year ago

(&#(*&%#%*%&!!!

Attached wrong copy...correct copy attached...my bad.

#3
Updated by Tod Beardsley over 1 year ago

  • Category set to general
  • Assignee set to Tod Beardsley

Most scanners presume that a RST or other connection fail is the end of the show, but this shouldn't be too hard to implement.

#4
Updated by Thomas Ring over 1 year ago

Yes that would be true if only checking one port on one system; however, if you are checking say ports 1521-1526 on a system...just because 1521 isn't listening, doesn't mean a later port isn't...so you would want continue on checking the other ports rather than skipping the entire host.

Also available in: Atom PDF