nerdexam
EC-Council

312-50V10 · Question #524

Jack was attempting to fingerprint all machines in the network using the following Nmap syntax: invictus@victim_server:~$ nmap -T4 -0 10.10.0.0/24 TCP/IP fingerprinting (for OS scan) xxxxxxx xxxxxx xx

The correct answer is A. OS Scan requires root privileges. Nmap's OS detection feature (-O flag) requires root or administrator privileges because it must craft and send raw packets, which is a privileged operation on Unix-based systems.

Scanning Networks

Question

Jack was attempting to fingerprint all machines in the network using the following Nmap syntax:

invictus@victim_server:~$ nmap -T4 -0 10.10.0.0/24 TCP/IP fingerprinting (for OS scan) xxxxxxx xxxxxx xxxxxxxxx. QUITTING! Obviously, it is not going through. What is the issue here?

Options

  • AOS Scan requires root privileges
  • BThe nmap syntax is wrong.
  • CThe outgoing TCP/IP fingerprinting is blocked by the host firewall
  • DThis is a common behavior for a corrupted nmap application

How the community answered

(57 responses)
  • A
    88% (50)
  • B
    4% (2)
  • C
    7% (4)
  • D
    2% (1)

Why each option

Nmap's OS detection feature (-O flag) requires root or administrator privileges because it must craft and send raw packets, which is a privileged operation on Unix-based systems.

AOS Scan requires root privilegesCorrect

The -O flag enables OS fingerprinting by sending specially crafted raw TCP/IP packets and analyzing responses, an operation that requires raw socket access. On Linux and Unix systems, raw socket creation is restricted to the root user, so running the scan as a non-root user causes Nmap to abort with the 'QUITTING!' error shown in the question.

BThe nmap syntax is wrong.

The Nmap syntax is functionally correct - the -T4 timing flag and CIDR target range are valid; the only issue is the privilege level of the user running the command.

CThe outgoing TCP/IP fingerprinting is blocked by the host firewall

The error message shown is a local privilege error from Nmap itself, not a firewall block - a host firewall would produce a different behavior such as filtered or dropped packets.

DThis is a common behavior for a corrupted nmap application

The 'QUITTING!' message is standard Nmap output for insufficient privileges and does not indicate application corruption.

Concept tested: Nmap OS detection root privilege requirement

Source: https://nmap.org/book/man-os-detection.html

Topics

#Nmap#OS fingerprinting#root privileges#network scanning

Community Discussion

No community discussion yet for this question.

Full 312-50V10 Practice