A TCP NULL packet has no TCP flags set. This is an illegal configuration in that "no flags" is undefined in the TCP specification (RFC 793). Modern security gateways will automatically reject TCP NULL packets as a bad packet. You may be able to configure a security gateway to allow TCP NULL packets. TCP NULL scans are used to determine the type of TCP stack used by a network port and not for sneaking packets past a (modern) firewall.
I found a case where a firewall would need to be configured to allow TCP NULL packets. It seems that there are some Linux (and possibly UNIX as well) TCP/IP stacks that accepts NULL packets as if they were ACK packets, although this behavior is not specified in RFC 793. I'm guessing someone made an accidental coding error (or a deliberate decision) when the stack was written and it became a feature that would break backward compatibility it is were "fixed."
Comments
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray
Forum Admin at www.techexams.net
--
LinkedIn: www.linkedin.com/in/jamesdmurray
Twitter: www.twitter.com/jdmurray