During an SMTP enumeration, a penetration tester connects to the mail server on port 25 and issues the commands 'VRFY root', 'EXPN admin', and 'RCPT TO:unknown@domain.com'. The server responds with '252' for VRFY, '250' for EXPN, and '550' for RCPT TO. What does this indicate?
This option correctly interprets the standard SMTP response codes observed during enumeration. A VRFY command returning '252' indicates that the server recognizes the user (e.g., 'root') but cannot verify their status, often implying the account exists but is disabled or restricted. An EXPN command receiving a '250' response confirms the existence of a mailing list or alias (e.g., 'admin') and typically provides its expansion. Conversely, a RCPT TO command resulting in a '550' error explicitly signifies that the specified recipient (e.g., 'unknown@domain.com') does not exist on the server, providing clear non-existence confirmation.
Why this answer
The SMTP response code 252 for VRFY root typically indicates that the user exists but is disabled or cannot receive mail at this time (the server knows the user but restricts verification). A 250 response for EXPN admin confirms that the admin mailing list exists. The 550 response for RCPT TO:unknown@domain.com definitively indicates that the recipient does not exist on the server.
Therefore, option A correctly interprets these responses: root exists but is disabled, the admin list exists, and the unknown user does not exist.
Exam trap
EC-CEH often tests the misinterpretation of SMTP response codes, where candidates confuse 252 (cannot verify but not denying existence) with a definitive 'user exists' or 'user disabled' status, or assume any non-250 response indicates a server misconfiguration like open relay.
How to eliminate wrong answers
Option B is wrong because open relay is tested by sending a message to an external domain via the server, not by VRFY, EXPN, or RCPT TO responses; a 550 for an unknown local user does not indicate relay behavior. Option C is wrong because SMTP injection involves injecting malicious commands or headers into SMTP transactions, which is not indicated by standard response codes 252, 250, and 550. Option D is wrong because the server is clearly running SMTP, as it responds to SMTP commands on port 25 with valid SMTP status codes.