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

The correct answer is C, Bollards. Bollards are physical security controls designed to prevent vehicles from entering restricted areas or crashing into buildings, entrances, sensitive facilities, or pedestrian zones. They are commonly installed outside government buildings, data centers, banks, airports, and other critical infrastructure locations to mitigate vehicle-borne threats and unauthorized vehicle access. Depending on the security requirement, bollards may be fixed, removable, retractable, or reinforced to withstand high-impact collisions.

In CEH physical security concepts, organizations use preventive physical controls to protect personnel, equipment, and facilities from unauthorized access and physical attacks. Bollards are considered perimeter security controls because they create a physical barrier between vehicles and protected assets. A receptionist provides administrative access control but cannot physically stop a vehicle. A mantrap is an access-control vestibule used to restrict and verify personnel entry. A turnstile controls pedestrian movement and helps prevent tailgating. Since the question specifically asks about stopping vehicles from crashing through building doors, bollards are the most appropriate and effective security feature.

Answer: C

The correct answer is C because allowing deprecated SSH ciphers creates a cryptographic weakness that can expose the system to downgrade-style attacks. SSH is intended to provide secure remote administration over TCP port 22 and relies on cryptographic protection for confidentiality and secure communication. CEH secure communication topics describe SSH as a secured alternative to Telnet using public-key cryptography for encryption. When obsolete or weak ciphers remain enabled, an attacker positioned in the communication path may try to influence negotiation so that the client and server use a weaker encryption option instead of a stronger one. CEH cryptography attack examples such as FREAK and POODLE show the same principle: attackers abuse fallback or weak algorithm support to force communication toward weaker encryption. This does not directly indicate DoS, XSS, or SQL injection. The primary risk from deprecated SSH ciphers is weakened encrypted communication and possible downgrade attacks.

The correct answer is B. Design Flaws.

The issue is caused by a weakness in the workflow logic of the application. The platform depends on a multi-step identity verification sequence, but the server does not properly enforce completion of each required stage. This is not simply a missing patch or configuration issue; it is a logic/design weakness in how the authentication workflow was built.

CEH-aligned vulnerability material classifies Design Flaws as flaws involving encryption, data validation, logic flaws, and similar systemic weaknesses . CEH web application material also explains that business logic flaws can exist in how an application is designed to function and may be exploited through transaction tampering or incomplete validation of workflow behavior .

Option A. Poor Patch Management is incorrect because the weakness is not described as an unpatched known vulnerability.

Option C. Application Flaws is related, but the more precise classification is a design or business logic flaw because the workflow itself fails to enforce required verification stages.

Option D. Misconfigurations / Weak Configurations is incorrect because the problem is not caused by insecure server settings or default configuration.

Option B. Design Flaws is correct because the root weakness is flawed authentication workflow logic.

Therefore, the best answer is B. Design Flaws.

AES is the industry-standard symmetric encryption algorithm endorsed by CEH v13. It provides strong confidentiality and resists traffic analysis when used with proper modes (e.g., CBC, GCM).

DES is obsolete, HMAC ensures integrity not encryption, PSA is not a standard encryption algorithm.

Thus, Option B is correct.

Ethical hacking, as defined throughout CEH courseware, is the authorized and legitimate process of identifying vulnerabilities, weaknesses, and misconfigurations in information systems. The primary objective is to strengthen security by discovering issues before malicious actors can exploit them. Ethical hackers follow strict legal guidelines, obtain written permission, and operate within a defined scope to ensure their activities contribute positively to the organization’s security posture. Unlike malicious hacking, the intent is not to steal data, cause harm, or disrupt operations. Ethical hackers use the same tools, techniques, and methodologies that attackers use, but with the purpose of remediation and risk reduction. CEH emphasizes that ethical hacking supports defense-in-depth strategies by enabling organizations to harden their environments and proactively mitigate threats. Therefore, identifying and fixing vulnerabilities is the central mission of ethical hacking.

The scenario clearly describes baiting, a physical social engineering technique covered in CEH under human-based attacks. Baiting involves enticing a victim with something appealing or intriguing, such as free software, confidential documents, or valuable information, in order to trick them into compromising security. In this case, the USB drive is deliberately labeled “Confidential 2025 Budget Plans,” which is designed to trigger curiosity and urgency. The attacker relies on human psychology, specifically curiosity and perceived importance, to motivate the target to plug the device into a company system.

Unlike phishing, which typically occurs through email or electronic communication, baiting often involves physical media such as USB drives left in public areas like parking lots or lobbies. CEH materials highlight that attackers may preload such devices with malware that executes automatically when inserted, granting access to the internal network. Even though this experiment uses a harmless tracking script, the methodology mirrors real-world attacks where malicious payloads could establish backdoors, exfiltrate data, or deploy ransomware.

Hoaxes spread false warnings to create panic but do not necessarily require interaction with physical devices. Pretexting involves fabricating a scenario or identity to elicit information directly from a target through conversation or interaction. The use of a strategically placed USB labeled with enticing information fits the definition of baiting precisely. This test reinforces the importance of policies prohibiting unknown removable media usage and promoting employee awareness training.

The correct answer is C. Capability.

In the Diamond Model of Intrusion Analysis, the four core elements are Adversary, Infrastructure, Capability, and Victim. The Capability element represents the tools, techniques, malware, exploits, procedures, and technical methods used by the adversary to carry out the attack.

Option A. Adversary is incorrect because it represents the attacker, threat actor, or organization responsible for the intrusion.

Option B. Infrastructure is incorrect because it represents the systems, domains, IP addresses, command-and-control servers, or delivery mechanisms used to conduct the operation.

Option D. Victim is incorrect because it represents the target entity, affected system, user, or business unit.

Therefore, the best answer is C. Capability.

A Directory Traversal attack, also known as path traversal, exploits weaknesses in how a web server or web application processes user-supplied file and directory paths through URLs or parameters. In CEH-aligned terminology, the attacker crafts requests that use traversal sequences such as dot-dot-slash patterns or encoded equivalents to escape the intended web root or permitted directory and reach sensitive locations on the underlying file system. The question states Sofia “manipulates resource paths” and successfully accesses “restricted system files,” revealing “sensitive configuration data.” This is the defining outcome of directory traversal: unauthorized access to files that should never be directly retrievable via the web interface, including application configuration files, server configuration, environment files, or other OS-level resources.

The prompt also eliminates other options by describing what the issue is not. It is not header manipulation, which would be more consistent with HTTP response splitting or header injection behaviors. It is not cached content tampering, which points to web cache poisoning. It is not credential compromise, which would indicate password cracking. Instead, the root cause is explicitly “failure to validate input paths,” matching CEH emphasis on inadequate input validation and improper path normalization or canonicalization before file access. Defensive guidance typically focuses on strict allowlisting of accessible resources, canonicalizing paths and enforcing a fixed base directory, blocking traversal tokens and their encoded forms, using indirect references instead of raw file paths, and applying least-privilege permissions to reduce impact if traversal is attempted.