Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Development: RE: Bug in IP Parsing

RE: Bug in IP Parsing

From: Brandon Enright <bmenrigh_at_ucsd.edu>
Date: Thu, 20 Oct 2005 12:14:29 -0700

  Juan Perez wrote:
>
> There seems to be a bug in the IP parsing mechanism.
>
> Example:
>
> input file: test
>
> test is only two lines:
>
> 10.10.0.0/24
> 10.10.0.80/24
>
> The bug is that the second line is an invalid combination and
> therefore should be rejected.Instead, nmap ignores the last
> octet(80) and proceeds to parse it as 10.10.0.0/24 .
>

This is not a bug. The /24 specifies that only the first 24 bits of
10.10.0.80 are significant. A simple AND with the bitmask results in
10.10.0.0.

See RFCs 1517, 1518, 1519, and 1520 for more information.

Regards,

Brandon

--
Brandon Enright
UCSD ACS/Network Operations
bmenrigh_at_ucsd.edu
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Received on Oct 20 2005
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos