312-50v13 Exam Dumps - Certified Ethical Hacker Exam (CEHv13)

A Rogue DHCP Server attack best fits the symptoms because it directly explains unexpected gateway changes, IP conflicts, and traffic redirection to deceptive portals. In CEH network attack coverage, DHCP is a foundational service that automatically provides clients with IP configuration such as IP address, subnet mask, default gateway, and DNS servers. If an attacker introduces a rogue DHCP server on the same broadcast domain, clients may accept leases from the rogue server—especially if it responds faster than the legitimate DHCP infrastructure. Once that happens, the attacker can push a malicious default gateway or DNS server to victims. This allows redirection of traffic, man-in-the-middle positioning, and phishing-style interception, which matches the “unfamiliar gateway settings” and “misleading login portals” described.

The mention of “temporary IP address conflicts” also aligns: a rogue server can hand out addresses that overlap with legitimate allocations, causing intermittent connectivity issues and failed connection attempts. While a DHCP starvation attack can create disruption by exhausting the DHCP pool, the key difference is outcome: starvation primarily denies service until a rogue server takes over. Here, the defining observable behavior is not just outage—it is misconfiguration and redirection, which points to the presence of a rogue DHCP server actively issuing malicious leases.

Packet sniffing alone would not change gateway settings, and MAC flooding is aimed at forcing switches to behave like hubs, not issuing IP configuration. Defensive controls include DHCP snooping, port security, network segmentation, and monitoring for unauthorized DHCP offers and anomalous lease patterns.

The correct answer is D. Post-Exploitation.

The scenario clearly occurs after initial access has already been obtained. The tester is no longer only discovering assets, identifying vulnerabilities, or exploiting the first weakness. Instead, the tester is modifying logging configurations, creating alternate access keys, maintaining persistence, and mapping privilege relationships inside the cloud tenant.

This aligns with the post-exploitation stage, where the tester evaluates what can be done after compromise, including maintaining access, enumerating privileges, understanding internal trust relationships, and documenting the impact of the compromise.

CEH-aligned methodology separates early activities such as information gathering and vulnerability scanning from later phases such as gaining access and maintaining access. The referenced methodology describes information gathering as collecting details such as IP addressing, protocols, open ports, device types, and vendor information, while later phases include gaining access, privilege escalation, backdoor installation, maintaining access, clearing logs, and covering tracks .

Option A. Exploitation is incorrect because exploitation is the phase where the initial vulnerability is actively used to gain access. In this scenario, the exposed credential has already been used.

Option B. Information Gathering is incorrect because the tester is not merely collecting external or pre-compromise information. The activity is taking place inside the cloud tenant after compromise.

Option C. Vulnerability Assessment is incorrect because vulnerability assessment focuses on identifying and validating weaknesses, not persistence, access key creation, or internal privilege mapping.

Option D. Post-Exploitation is correct because the tester is operating after compromise to maintain access and assess the internal impact.

Therefore, the best answer is D. Post-Exploitation.

The CEH Enumeration module explains that SMTP supports commands such as VRFY, EXPN, and RCPT TO, which can be abused to enumerate valid email users if not properly restricted.

In this scenario, the smtp-enum-users Nmap script successfully uses EXPN and RCPT, indicating that the server responds differently to valid and invalid usernames.

Option C is correct because unrestricted SMTP user verification allows attackers to harvest usernames for further attacks such as phishing or brute force.

Option A involves authentication, not enumeration.

Option B affects confidentiality, not user discovery.

Option D is unrelated to SMTP enumeration.

CEH strongly recommends disabling or restricting these SMTP commands.

The correct answer is D. ntpq -p [host].

The scenario requires querying the active NTP service to review its current associations and operational state. The ntpq utility is designed to query and monitor the NTP daemon. CEH-aligned NTP enumeration material states that ntpq is a command-line utility used to query the NTP server, monitor ntpd operations, and determine performance. It also states that the -p option prints a list of peers known to the server and summarizes their state .

Option A. ntptrace is incorrect because ntptrace follows the chain of NTP servers back to the primary time source. The scenario specifically says Kevin is not tracing the upstream hierarchy.

Option B. ntpq [-inp] [-c command] [host] [...] is a general syntax form for ntpq, but the most precise command for viewing peer associations and state is ntpq -p [host].

Option C. ntpdc is incorrect because although ntpdc can query ntpd, it is more associated with querying daemon state and requesting state changes. The question asks for the command to review current associations and operational status, which is most directly matched by ntpq -p.

Option D. ntpq -p [host] is correct because it directly queries the NTP service and prints peer association/status information.

Therefore, the best answer is D. ntpq -p [host].

The correct answer is Credentialed Scanning. CEH vulnerability assessment guidance explains that credentialed scans use authorized login access on the target system so the scanner can inspect the machine from the inside with a much higher level of accuracy and detail. That is why credentialed scanning can identify installed updates, local policy settings, configuration inconsistencies, file permissions, registry issues, and patch gaps that are not always visible from an external network perspective. The question specifically mentions granular host-level findings that required direct system-level inspection, which is a strong indicator that valid credentials were used to query the target systems. Non-credentialed scanning, by contrast, relies on remote observation and network-visible characteristics, so it generally cannot provide the same depth of internal host information. Automated scanning is too broad a label, and application scanning is limited to application-layer targets rather than host operating-system posture. CEH materials consistently note that credentialed scans produce more accurate vulnerability results and reduce false positives because the scanner can verify software versions, patch states, and security settings directly on the target machine rather than merely inferring them from banners or exposed services.

The correct answer is A. Stolen equipment. In CEH ethical hacking methodology, “stolen equipment” is a mode of ethical hacking that simulates theft of a critical information resource, such as a laptop owned by an important organizational user, and then provides that asset to the ethical hacker for assessment. The question specifically mentions targeting the CEO’s laptop or backup tapes to extract critical information, usernames, and passwords. These are classic examples of sensitive assets that may contain cached credentials, confidential documents, password hashes, VPN profiles, email archives, or backup copies of production data. This test evaluates whether protections such as full-disk encryption, strong authentication, secure backup handling, and data-at-rest controls are effective. “Physical entry” focuses on entering and compromising the organization’s facilities or ICT infrastructure, while “insider attack” simulates a trusted internal user abusing access. “Outsider attack” typically represents an external threat. Because the focus is on stolen laptops and backup media, the best CEH answer is stolen equipment.

CEH v13 identifies Idle (Zombie) Scanning as one of the most stealthy reconnaissance techniques. In this method, attackers use a third-party system (the zombie) to send probes to the target, obscuring the attacker’s true identity.

Because the attacker never directly interacts with the target, detection and attribution become extremely difficult. FIN and Xmas scans are stealthy but still originate from the attacker’s IP. TCP connect scans are noisy and easily detected.

CEH v13 highlights idle scanning as the gold standard for stealth reconnaissance, making option D correct.

The correct answer is A. Insecure Ecosystem Interfaces.

The weakness involves externally reachable components that interact with management platforms and expose administrative configuration functions. These components also suffer from insufficient input validation and weak authentication controls. This aligns with Insecure Ecosystem Interfaces, which covers insecure web, cloud, mobile, API, and backend interfaces that form part of the IoT device ecosystem.

CEH-aligned IoT material identifies vulnerable interfaces as a major IoT challenge and lists OWASP IoT categories including insecure web, cloud, and mobile interfaces, insufficient authentication/authorization, and insecure network services . It also explains that insecure cloud and mobile interfaces are associated with weak credentials, account enumeration, and poor interface protection . In the newer OWASP IoT wording, these interface weaknesses are commonly grouped under Insecure Ecosystem Interfaces.

Option B. Insecure Default Settings is incorrect because the scenario does not focus on default passwords, default configurations, unnecessary enabled services, or insecure factory settings.

Option C. Insecure Network Services is incorrect because that category focuses on vulnerable network services exposed by the device, such as services susceptible to buffer overflow or denial-of-service conditions. The scenario emphasizes external ecosystem components and management interfaces.

Option D. Lack of Device Management is incorrect because the scenario does not describe missing inventory, missing update management, missing decommissioning, or inability to monitor device lifecycle.

Therefore, the best answer is A. Insecure Ecosystem Interfaces.