Re: [NSE] Undeclared variable in dns.processResponse()

[Patrik Karlsson <patrik () cqure net>]

On 29 okt 2010, at 17.20, Ron wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, 29 Oct 2010 17:04:53 +0200 Patrik Karlsson <patrik () cqure net> wrote:
> > I can't reproduce this. This is what I'm getting:
> >
> > AbuseX:nmap-dev patrik$ ./nmap --script test.nse -d
> >
> > Starting Nmap 5.35DC18 ( http://nmap.org ) at 2010-10-29 17:03 CEST
> > PORTS: Using top 1000 ports found open (TCP:1000, UDP:0, SCTP:0)
> > --------------- Timing report ---------------
> >  hostgroups: min 1, max 100000
> >  rtt-timeouts: init 1000, min 100, max 10000
> >  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
> >  parallelism: min 0, max 0
> >  max-retries: 10, host-timeout: 0
> >  min-rate: 0, max-rate: 0
> > ---------------------------------------------
> > NSE: Loaded 1 scripts for scanning.
> > NSE: Script Pre-scanning.
> > NSE: Starting runlevel 1 (of 1) scan.
> > Initiating NSE at 17:03
> > NSE: NSE Script Threads (1) running:
> > NSE: Starting test.
> > mass_rdns: Using DNS server 10.0.200.1
> > NSE: dns.query() got zero responses attempting to resolve query:
> > www.obscuredomain.com NSE: Finished test.
> > Completed NSE at 17:03, 8.00s elapsed
> > NSE: Script Post-scanning.
> > Read from .: nmap-services.
> > WARNING: No targets were specified, so 0 hosts scanned.
> > Nmap done: 0 IP addresses (0 hosts up) scanned in 8.07 seconds
> >
> > Can you share a packet capture from when the error occurs?
> >
> > //Patrik
>
> Perhaps it's because of how my DNS servers response?
>
> I'm sending you a pcap off list. 
>
> Ron
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.16 (GNU/Linux)
>
> iEYEARECAAYFAkzK5kgACgkQ2t2zxlt4g/Qn7gCeKhSyizkCoKzdGSQ3/ZOydHXn
> WgoAn1ES8+sUPl1yPBjQYdWkpbc85ix8
> =121D
> -----END PGP SIGNATURE-----
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/


Ok, I think I finally fixed it. It looks as if the bug was introduced in r14493 so unfortunately I can't take credit 
for this one ;)
I've commited an updated version that solves the problem as r20847. Let me know if this works for you.

//Patrik
--
Patrik Karlsson
http://www.cqure.net
http://www.twitter.com/nevdull77





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