ECCouncil Updated 312-50v13 Exam Questions and Answers by katie

According to CEH v13 System Hacking and Web Application Hacking, once reconnaissance and footprinting are complete, attackers typically move into controlled exploitation while maintaining stealth. Since the CEH has already identified a session hijacking vulnerability, leveraging that weakness is the most logical and stealthy progression.

Session hijacking allows attackers to impersonate legitimate users without triggering authentication alerts, making it significantly less detectable than brute-force or scanning activities. Option B aligns with CEH methodology: hijacking a valid session provides authorized-level access, which can then be abused to make configuration changes discreetly.

SQL injection (Option A) may trigger database errors and IDS alerts. Brute-force attacks (Option C) are noisy and easily logged. Automated vulnerability scanning (Option D) generates excessive traffic and is typically avoided once exploitation begins.

CEH v13 emphasizes using already-identified weaknesses and minimizing footprint during exploitation. Therefore, Option B is correct.

Rachel is using the Ping method for sniffer detection. The distinguishing behavior in the scenario is that she sends ICMP echo requests (pings) crafted so that the Layer 2 MAC address is incorrect/mismatched, while the Layer 3 IP destination is correct. Under normal circumstances, a host’s network interface card (NIC) should drop frames not addressed to its MAC address. However, when a NIC is set to promiscuous mode (as sniffers often require), it can accept frames regardless of destination MAC and pass them up the stack. If the operating system then processes the encapsulated IP packet and responds (e.g., sends an ICMP echo reply), that response suggests the host is accepting frames it normally would ignore—an indicator consistent with promiscuous mode sniffing.

This technique is used as a heuristic: by intentionally violating normal Ethernet delivery rules and observing whether the target still responds, you can infer that the interface may be capturing traffic not explicitly addressed to it. It’s not perfect—modern drivers, switches, VLAN configurations, and host firewall behavior can affect results—but the scenario’s “mismatched MAC but correct IP” plus “the suspected machine responds” is the classic signature of the ping-based promiscuous-mode test.

Why the other options are less suitable:

ARP method (B) typically involves ARP-based tricks (non-broadcast ARP requests or crafted ARP traffic) to test how the target responds; the scenario explicitly describes ICMP behavior.

DNS method (C) relates to DNS queries/resolution behavior and does not match the ICMP/MAC mismatch test.

Nmap sniffer-detect (NSE) (D) is a specific scripted approach, but the question asks for the underlying technique being used; the described action matches the Ping method.

Therefore, the correct answer is A. Ping Method.

The described content matches the Assessment Overview section because it focuses on how the vulnerability assessment was executed rather than what was found. An assessment report typically includes a part that explains the methodology and approach used to perform scanning so stakeholders can understand the process, validate coverage, and interpret results correctly. In this scenario, Nikhil is documenting the scanning methodology, target information, type and scope of scans, and the tools used. These elements provide context and transparency about the assessment process, assumptions, and boundaries—exactly what an overview is meant to capture.

This section is also intentionally not listing specific vulnerabilities or affected assets, which further confirms it is not the Findings section. Findings is where the report enumerates discovered vulnerabilities, affected systems, evidence, severity, and recommendations. Similarly, it is not the Risk Assessment section because that portion generally interprets the findings to determine likelihood and impact, prioritizes risks, and may map issues to business impact or compliance requirements. Since Nikhil is only describing the scanning approach and scope, risk analysis is premature and out of place.

Why not Supporting Information? Supporting information usually contains appendices or reference material that supplements the core report—such as raw scan outputs, detailed configuration data, asset inventories, screenshots, logs, tool configurations, or glossary/definitions. While tool names and technical details can appear there, the narrative about methodology, targets, scope, and scan types is more appropriately part of the main body’s overview so readers understand the assessment context before reviewing results.

Therefore, the section Nikhil is working on is C. Assessment Overview, which establishes the assessment context and explains the scanning approach prior to presenting findings and risk conclusions.

CEH courseware describes rootkits as specialized malware designed to conceal their presence while providing persistent, unauthorized access to system-level functions. Rootkits typically modify low-level components of the operating system—such as kernel modules, drivers, or system processes—to hide files, processes, registry keys, and network connections. Their primary purpose is to grant attackers administrative privileges without triggering alerts, making them extremely stealthy and dangerous. CEH emphasizes that rootkits often accompany other malware to maintain long-term control after initial compromise. In contrast, viruses replicate by attaching to files, keyloggers record keystrokes but do not hide system-level access, and ransomware encrypts data rather than conceals operations. The defining characteristics in this scenario—cloaking activity, providing admin-level control, persisting undetected—are directly aligned with rootkit behavior as described in CEH training material.