RE: [Plugins-writers] loose source routing problem

From: Scott Shebby (scotts@private)
Date: Wed Mar 03 2004 - 16:55:11 PST

  • Next message: Brian Morton: "[Plugins-writers] Interested in writing F-Secure Antivirus plugin"

    Cissper-
    
    As far as I can tell the test first trys a TCP and then a ICMP packet.
    Loose source routing is an IP option.
    
    Usually these types of packets are simply blocked or ignored.  It looks
    like the test sees if it gets a response back and if it does then flags
    the vuln.
    
    The test doesn’t go so far as to specify host to route through.  You can
    test this using the traceroute -g switch.  When you do that you are
    saying (eg:  -g host1) route my packet through host1.
    
    Another way to test the lsrr is to use hping -G --lsrr.
    
    Most likely your host is simply ignoring the lsrr flag and replying to
    the echo request.
    
    -Scott
    
    -----Original Message-----
    From: plugins-writers-bounces@private
    [mailto:plugins-writers-bounces@private] On Behalf Of cissper
    Sent: Tuesday, March 02, 2004 6:55 PM
    To: security-basics@private; plugins-writers@private;
    full-disclosure@private
    Subject: [Plugins-writers] loose source routing problem
    
    
    I am lost here! Almost every time when I perform a
    nessus scan I get this odd vulnerability: loose source
    routing identified.
    
    I really don’t know how that script works but I have
    to analyse if this is a false positive or not. When I
    perform a manual traceroute (UDP) to the destination
    host, I do not get all gateways listed. It looks
    similar to that (just as an example):
    
    1  helios.ee.lbl.gov (128.3.112.1)  0 ms  0 ms  0 ms
    2  lilacâdmc.Berkeley.EDU (128.32.216.1)  39 ms  19 ms
     39 ms
    3  lilacâdmc.Berkeley.EDU (128.32.216.1)  19 ms  39 ms
     19 ms
    4  ccngwânerâcc.Berkeley.EDU (128.32.136.23)  39 ms 
    40 ms  19 ms
    5  ccnânerif35.Berkeley.EDU (128.32.168.35)  39 ms  39
    ms  39 ms
    6  csgw.Berkeley.EDU (128.32.133.254)  39 ms  59 ms 
    39 ms
    7  * * *
    8  * * *
    
    
    How can the nessus plug-in reporting this
    vulnerability get through to the destination host with
    loose source routing when I can get through with ICMP
    and UDP???
    
    Can anybody explain me how this plug-in works? I just
    think it doesn’t work properly and always provides a
    false positive! In addiation, can anyone show how to
    reproduce what the script does?
    
    Your help is very much appreciated
    
    regards
    cissper
    
    loose source routing, unreliable results
    
    
    
    Find local movie times and trailers on Yahoo! Movies.
    http://au.movies.yahoo.com
    
    ------------------------------------------------------------------------
    ---
    Ethical Hacking at the InfoSec Institute. Mention this ad and get $545
    off 
    any course! All of our class sizes are guaranteed to be 10 students or
    less 
    to facilitate one-on-one interaction with one of our expert instructors.
    
    Attend a course taught by an expert instructor with years of
    in-the-field 
    pen testing experience in our state of the art hacking lab. Master the
    skills 
    of an Ethical Hacker to better assess the security of your organization.
    
    Visit us at: 
    http://www.infosecinstitute.com/courses/ethical_hacking_training.htm
    ------------------------------------------------------------------------
    ----
    
    _______________________________________________
    Plugins-writers mailing list
    Plugins-writers@private
    http://mail.nessus.org/mailman/listinfo/plugins-writers
    
    
    
    _______________________________________________
    Plugins-writers mailing list
    Plugins-writers@private
    http://mail.nessus.org/mailman/listinfo/plugins-writers
    



    This archive was generated by hypermail 2b30 : Wed Mar 03 2004 - 16:50:56 PST