ECCouncil 312-50v13 (Certified Ethical Hacker v13) Practice Test 1

Question 1

For the topic of OAuth redirect validation, which operational explanation is accurate?

  1. Open redirect registration can misdeliver authorization responses or codes outside the intended client origin.
  2. Function authorization requires server-side role checks independent of hidden menus or client display logic.
  3. Object-level authorization fails when the server trusts a client-chosen identifier without checking ownership.
  4. State-changing form endpoints are vulnerable when ambient cookies alone authorize cross-origin requests.

Explanation

Correct Answer

A:

An authentication broker accepts an attacker-specified redirect destination when issuing authorization responses; that situation illustrates the actual operating behavior under review. Its practical safeguard is to require exact approved redirect URIs and validate OAuth state and PKCE as appropriate, with confirmation when authorization requests with unregistered redirects fail before codes are returned to those destinations.

Incorrect Answers

B:

A regular user reaches an administrator-only action by directly calling its API route; those details characterize function-level authorization flaw and would call for check authorization on each privileged operation and deny unentitled roles server-side, rather than explaining OAuth redirect validation.

C:

A signed-in customer changes a record identifier and sees another customer's invoice; those details characterize object-level authorization flaw and would call for enforce per-object access policy for every data retrieval and modification request, rather than explaining OAuth redirect validation.

D:

A browser submits a password-change form while the user is logged in but without evidence of intended action; those details characterize cross-site request forgery in forms and would call for verify anti-CSRF tokens and origin context for browser-based state-changing operations, rather than explaining OAuth redirect validation.

Question 2

A validation plan targets captive portal limitations. What result would demonstrate the specified protective boundary?

  1. Wireless accounting records tie each accepted connection to an authorized user or device identity.
  2. Managed clients reject lookalike access points whose authentication-server identity is not trusted.
  3. Test devices without valid client credentials are rejected and users cannot bypass server trust checks.
  4. Application connections negotiate authenticated encryption after captive-portal completion.

Explanation

Correct Answer

D:

Captive portals provide access workflow, not end-to-end confidentiality or strong device authentication; the outcome tests this precise property in the production control. It relates to the original observation that an airport network displays a terms page, and users assume the portal itself encrypts all subsequent traffic.

Incorrect Answers

A:

Enterprise WLAN access uses 802.1X and an authentication backend to manage per-identity access; that evidence is relevant when a corporate wireless network needs distinct user or device identities instead of one shared password, but does not establish closure of the captive portal limitations exposure.

B:

An evil-twin AP impersonates a trusted network name to attract client associations or credentials; that evidence is relevant when a laptop connects to a nearby access point using the company SSID but an unfamiliar certificate and controller, but does not establish closure of the captive portal limitations exposure.

C:

EAP-TLS uses certificate-based mutual authentication when client and server trust are properly validated; that evidence is relevant when managed laptops must authenticate to enterprise Wi-Fi without sending reusable user passwords, but does not establish closure of the captive portal limitations exposure.

Question 3

A finding concerns infrastructure-as-code drift. Select the explanation that captures how this issue or control works.

  1. Managed key services help separate protected key access, rotation policy, and audit from application source code.
  2. Manual cloud changes create configuration drift outside version-controlled infrastructure definitions.
  3. Cloud service providers secure assigned infrastructure layers while customers remain accountable for their configurations and data.
  4. Centralized secrets services support scoped retrieval and lifecycle controls instead of source-controlled credentials.

Explanation

Correct Answer

B:

A manually created public firewall rule appears in production but is absent from the reviewed deployment configuration; that situation illustrates the actual operating behavior under review. Its practical safeguard is to detect drift and reconcile production with reviewed infrastructure-as-code changes, with confirmation when drift scans show runtime firewall rules match approved deployment manifests after reconciliation.

Incorrect Answers

A:

Application data is encrypted but the same long-lived encryption key is hardcoded into its source repository; those details characterize cloud key management and would call for use a managed key service with limited decrypt grants and remove exposed embedded keys, rather than explaining infrastructure-as-code drift.

C:

A hosted database customer assumes the provider also determines application user permissions and data retention; those details characterize cloud shared responsibility and would call for document the service-model responsibility split and enforce customer-side identity and data controls, rather than explaining infrastructure-as-code drift.

D:

Multiple microservices copy shared database credentials into environment files committed with deployment manifests; those details characterize cloud secrets distribution and would call for use secret management with workload identity and limit retrieval to the requesting application, rather than explaining infrastructure-as-code drift.

Question 4

A trainee confuses several related concepts with Kubernetes admission guardrails. Which explanation resolves that confusion?

  1. Cloud workload firewalls or security groups constrain permitted instance traffic and may track connection state.
  2. Admission controls evaluate proposed resources at creation and can enforce workload security constraints.
  3. Containers share host kernel resources, so excessive privileges and mounts weaken isolation boundaries.
  4. Cloud security posture management compares cloud settings with policy baselines and aggregates misconfiguration findings.

Explanation

Correct Answer

B:

A cluster accepts workloads with host-level privileges despite published organizational security requirements; that situation illustrates the actual operating behavior under review. Its practical safeguard is to apply Pod Security Admission standards or maintained validating admission policies for the cluster version, with confirmation when test deployments requesting forbidden host access fail admission before scheduling.

Incorrect Answers

A:

A virtual machine accepts administrative traffic from every internet address because of an overly broad inbound rule; those details characterize cloud network security groups and would call for limit administrative ingress to approved bastion or management source ranges, rather than explaining Kubernetes admission guardrails.

C:

A containerized service runs privileged with broad host filesystem mounts even though it only serves web traffic; those details characterize container runtime boundaries and would call for drop unnecessary capabilities and enforce restricted runtime settings and filesystem access, rather than explaining Kubernetes admission guardrails.

D:

An organization wants continuous visibility into risky storage, identity, and network configurations across many accounts; those details characterize cloud security posture assessment and would call for continuously assess account configuration baselines and route accountable findings to owners, rather than explaining Kubernetes admission guardrails.

Question 5

Which mechanism should a defender associate with port-to-service mismatch?

  1. Application banners can identify probable services but may be suppressed, customized, or misleading.
  2. IPv4 and IPv6 have separate addresses and filtering paths; protecting one family does not secure the other.
  3. Echo-response filtering can hide ping responses without proving that the host or its services are offline.
  4. Port numbers are conventions; application-layer content and process ownership establish actual service identity.
  5. Filtering or packet loss can prevent a conclusive TCP port-state observation from a remote position.
  6. Uninventoried listeners can expose control planes without ordinary maintenance or review.

Explanation

Correct Answer

D:

A responder finds an HTTP-speaking service listening on an unexpected numeric port; that situation illustrates the actual operating behavior under review. Its practical safeguard is to verify listener processes and application protocols rather than assigning services by port number alone, with confirmation when host socket inventory and an approved protocol exchange identify the true process and service.

Incorrect Answers

A:

A permitted service connection returns software product and version details in its greeting; those details characterize service banner identification and would call for reduce unnecessary version disclosure and corroborate service identity with authenticated inventory, rather than explaining port-to-service mismatch.

B:

An endpoint firewall protects IPv4 traffic but an unintended service is reachable over IPv6; those details characterize dual-stack IPv6 exposure and would call for apply equivalent tested network policy to both address families and document reachable IPv6 services, rather than explaining port-to-service mismatch.

C:

A monitored host does not answer ping but its approved application endpoint still accepts connections; those details characterize ICMP echo filtering and would call for confirm liveness through an authorized service check rather than treating missing echo replies as proof of absence, rather than explaining port-to-service mismatch.

E:

A probe to a specific port receives no response while other ports on the same host reply; those details characterize filtered TCP port and would call for use an approved alternate vantage point and inspect ACL logs to separate filtering from packet loss, rather than explaining port-to-service mismatch.

F:

A listening management interface appears on a newly provisioned host but is absent from the service catalog; those details characterize exposure from shadow services and would call for reconcile actual listeners with service ownership and remove or restrict unauthorized services, rather than explaining port-to-service mismatch.

Question 6

A validation plan targets least privilege. What result would demonstrate the specified protective boundary?

  1. A permission test shows the reporting identity can view dashboards but cannot change policy or user roles.
  2. Workflow logs show the requester and approver are different authorized identities.
  3. The inventory records owner, data category, business purpose, and handling requirements for the repository.
  4. Access reviews and file permissions show only approved roles can retrieve the protected records.

Explanation

Correct Answer

A:

Excess privileges enlarge the consequence of identity compromise beyond legitimate job requirements; the outcome tests this precise property in the production control. It relates to the original observation that a reporting account can edit security policies despite requiring only read access to dashboards.

Incorrect Answers

B:

Splitting incompatible responsibilities prevents one individual from completing a sensitive process without review; that evidence is relevant when one employee can request a high-risk production change and approve the same request, but does not establish closure of the least privilege exposure.

C:

Classification links information sensitivity and ownership to controls, retention, and handling requirements; that evidence is relevant when a test report finds a storage location containing regulated personal records but no assigned data owner, but does not establish closure of the least privilege exposure.

D:

Confidentiality concerns who may access information, even when the underlying records are accurate and available; that evidence is relevant when a captured troubleshooting file contains readable patient records accessible to an unrelated team, but does not establish closure of the least privilege exposure.

Question 7

A single approved remediation review covers 2 separately named requirements: (1) Asymmetric key roles; (2) Symmetric confidentiality. Which audit outcomes would directly demonstrate protection for those areas? Choose TWO.

  1. Object metadata contains wrapped data keys rather than exposed raw content-encryption keys.
  2. Negotiation records show ephemeral key agreement in use for approved client sessions.
  3. Status checks identify the compromised certificate as revoked and accept its valid replacement.
  4. Only the designated private-key holder can recover the protected secret in a controlled test.
  5. Recovery tests decrypt backups only with authorized key access and detect modified ciphertext.

Explanation

Correct Answers

D:

This verifies the asymmetric key roles component alongside asymmetric key roles in the combined audit: public-key cryptography can use a recipient's public key to establish confidentiality while the private key stays secret. For the asymmetric key roles audit set, the relevant observed case is that a sender needs to protect a short secret for a recipient without first sharing a symmetric key.

E:

This verifies the symmetric confidentiality component alongside asymmetric key roles in the combined audit: symmetric algorithms use a shared secret for encryption and decryption and are efficient for bulk data. For the asymmetric key roles audit set, the relevant observed case is that a large backup needs efficient encryption and decryption with the same protected secret key.

Incorrect Answers

A:

Envelope encryption encrypts bulk content with data keys and wraps those keys under a separate managed key; this result is evidence about envelope encryption when a storage platform encrypts each object with a short-lived data key protected by a central master key, not a direct closure test for the named asymmetric key roles, symmetric confidentiality requirements.

B:

Ephemeral key agreement can give forward secrecy by deriving session secrets independent of a recoverable long-term key; this result is evidence about TLS forward secrecy when a captured encrypted session should remain protected even if the server's long-term private key is exposed later, not a direct closure test for the named asymmetric key roles, symmetric confidentiality requirements.

C:

Revocation lets relying parties learn that an otherwise unexpired certificate should no longer be trusted; this result is evidence about certificate revocation status when a certificate's private key is compromised well before its scheduled expiration date, not a direct closure test for the named asymmetric key roles, symmetric confidentiality requirements.

Question 8

A follow-up audit focuses on DNS service enumeration. Which evidence most reliably demonstrates effective treatment?

  1. Unauthenticated listing requests cannot enumerate private directories on the file-transfer service.
  2. A low-privilege access test cannot list or open restricted shares while approved users retain access.
  3. Public resolver queries show only intentionally exposed records while internal records stay private.
  4. Network policy checks show public clients cannot query sensitive remote management bindings.

Explanation

Correct Answer

C:

DNS records may expose system naming and topology when public and internal views are mixed; the outcome tests this precise property in the production control. It relates to the original observation that an external reviewer learns internal-looking DNS names from a public-facing name service.

Incorrect Answers

A:

Anonymous FTP can publish files and names without identity verification or transport encryption; that evidence is relevant when an old file-transfer service exposes a directory listing to a user without authentication, but does not establish closure of the DNS service enumeration exposure.

B:

SMB share enumeration reveals network resource names and sometimes access permissions before file access is attempted; that evidence is relevant when a file server lists sensitive shared folders to users who do not need to know those names, but does not establish closure of the DNS service enumeration exposure.

D:

RPC endpoint information can reveal reachable management interfaces and service dependencies; that evidence is relevant when an endpoint lists remotely exposed interface identifiers and service bindings to unknown clients, but does not establish closure of the DNS service enumeration exposure.

Question 9

An analyst is sorting findings by mechanism. One entry reads: A directory service returns user and group details to an unauthenticated client connection. Which label is the right one?

  1. Kerberos service principals
  2. Public API directory listing
  3. Anonymous LDAP bind
  4. SNMP default communities

Explanation

Correct Answer

C:

LDAP directory reads can disclose identity structure when anonymous search rights are too broad; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to disable unnecessary anonymous directory searches and scope read permissions to approved identities, verified when unauthenticated directory queries return no sensitive users, group membership, or privileged attributes.

Incorrect Answers

A:

Service principal names map services to accounts and can indicate privileged service account exposure; this different classification would fit when a directory assessment reveals service principal names linked to high-value application identities, not the evidence pointing to anonymous LDAP bind in the question.

B:

Excessive API enumeration arises when list endpoints lack authorization or safe pagination and filtering; this different classification would fit when an administrative API lists internal user identifiers through an endpoint open to all clients, not the evidence pointing to anonymous LDAP bind in the question.

D:

Legacy SNMP community strings act as weak shared access tokens, especially without encryption; this different classification would fit when a network device exposes interface and configuration information through a shared default community string, not the evidence pointing to anonymous LDAP bind in the question.

Question 10

The assessment lead requests a precise definition of unauthenticated exposure assessment. Which technical interpretation fits?

  1. Risk acceptance needs accountable approval, defined scope, expiry, and reassessment triggers.
  2. Unauthenticated checks evaluate externally observable attack surfaces but may lack host-level configuration detail.
  3. Risk-based remediation SLAs translate vulnerability priority into accountable response deadlines and escalation.
  4. Authenticated assessments can inspect installed software and local configuration beyond remote service fingerprints.

Explanation

Correct Answer

B:

A defender wants to know which flaws are visible to an outsider who has no internal credentials; that situation illustrates the actual operating behavior under review. Its practical safeguard is to run approved external-facing assessments and record their limited visibility in risk results, with confirmation when findings identify exposed interfaces and services without claiming full knowledge of hidden local packages.

Incorrect Answers

A:

A business owner accepts an unresolved vulnerability with no review date or documented compensating control; those details characterize time-limited risk acceptance and would call for require a documented exception with business sign-off, control requirements, and automatic re-review, rather than explaining unauthenticated exposure assessment.

C:

A critical finding stays open for months because no team owns the fix or deadline; those details characterize remediation service level and would call for assign remediation owners and deadlines that reflect verified business exposure and severity, rather than explaining unauthenticated exposure assessment.

D:

A network-only scanner misses an outdated package visible in the server's local package inventory; those details characterize credentialed vulnerability assessment and would call for use narrowly scoped protected scan credentials to collect host configuration and patch evidence, rather than explaining unauthenticated exposure assessment.

Certified Ethical Hacker v13 (312-50v13) Practice Tests