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

Question 360

A client requests practical treatment for this condition: A browser script copies a URL fragment into innerHTML without a round trip through the server. Which measure is the closest match?

  1. Avoid native object deserialization from clients and use validated simple data contracts.
  2. Use safe text APIs and trusted sanitization instead of unsafe DOM HTML insertion.
  3. Validate file signatures and content, store uploads as inert data, and set safe download headers.
  4. Use role-aware server-side response schemas that expose only necessary authorized fields.
  5. Apply context-appropriate output encoding and avoid inserting untrusted input into executable HTML contexts.

Explanation

Correct Answer

B:

DOM XSS arises when client-side code sends attacker-controlled values into dangerous browser sinks; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that instrumented browser tests show untrusted fragment data displayed without creating active markup.

Incorrect Answers

A:

Deserialization of untrusted object graphs can trigger unsafe code paths or unexpected property changes; the proposed safeguard addresses a case where an application reconstructs complex server objects directly from untrusted client-supplied serialized data, rather than the dom-based cross-site scripting finding described here.

C:

Uploads can create script, stored-XSS, or malware exposure when the server trusts names and client media types; the proposed safeguard addresses a case where an avatar service accepts an arbitrary extension and serves the uploaded file with an active browser content type, rather than the dom-based cross-site scripting finding described here.

D:

Sensitive fields remain exposed when authorization and output filtering occur only in the browser; the proposed safeguard addresses a case where a customer profile endpoint returns staff-only flags and internal identifiers even though the UI hides them, rather than the dom-based cross-site scripting finding described here.

E:

Reflected XSS occurs when request-derived content is immediately returned without suitable output encoding; the proposed safeguard addresses a case where a query value is copied into an HTML response and interpreted by the browser as executable markup, rather than the dom-based cross-site scripting finding described here.

Question 361

An authorized security review records the following: A mail security report shows messages rejected when visible sender identity fails domain alignment checks. Which concept most accurately classifies the observation?

  1. DKIM signature verification
  2. Email header tracing
  3. DMARC email alignment
  4. RDAP registration lookup

Explanation

Correct Answer

C:

DMARC evaluates alignment with SPF or DKIM and lets the domain owner publish reporting and handling policy; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to configure DMARC reporting and an enforcement policy appropriate to the domain's readiness, verified when aggregate reports show legitimate aligned traffic and policy handling of spoofed sender identities.

Incorrect Answers

A:

DKIM binds selected message headers and body content to a signing domain using a published public key; this different classification would fit when an outbound message carries a domain-associated cryptographic signature that receiving mail servers can verify, not the evidence pointing to DMARC email alignment in the question.

B:

Received headers, authentication results, and server traces can reveal message path and origin clues; this different classification would fit when an investigator reads the received-hop chain to distinguish real mail transit from a forged display name, not the evidence pointing to DMARC email alignment in the question.

D:

RDAP provides structured registration data over HTTPS with access controls and standardized responses; this different classification would fit when an asset owner wants standardized registration records for a domain without relying on old free-form WHOIS formatting, not the evidence pointing to DMARC email alignment in the question.

Question 362

A system owner needs a response to this observation: An authentication broker accepts an attacker-specified redirect destination when issuing authorization responses. Which step directly meets the need?

  1. Verify anti-CSRF tokens and origin context for browser-based state-changing operations.
  2. Check authorization on each privileged operation and deny unentitled roles server-side.
  3. Require exact approved redirect URIs and validate OAuth state and PKCE as appropriate.
  4. Allowlist specific trusted origins and avoid wildcard or reflected credentialed origin permissions.

Explanation

Correct Answer

C:

Open redirect registration can misdeliver authorization responses or codes outside the intended client origin; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that authorization requests with unregistered redirects fail before codes are returned to those destinations.

Incorrect Answers

A:

State-changing form endpoints are vulnerable when ambient cookies alone authorize cross-origin requests; the proposed safeguard addresses a case where a browser submits a password-change form while the user is logged in but without evidence of intended action, rather than the OAuth redirect validation finding described here.

B:

Function authorization requires server-side role checks independent of hidden menus or client display logic; the proposed safeguard addresses a case where a regular user reaches an administrator-only action by directly calling its API route, rather than the OAuth redirect validation finding described here.

D:

Unsafe CORS policies may let untrusted websites read authenticated cross-origin responses in browsers; the proposed safeguard addresses a case where an API reflects arbitrary Origin headers while permitting browsers to include credentials in cross-origin requests, rather than the OAuth redirect validation finding described here.

Question 363

A single approved remediation review covers 2 separately named requirements: (1) Anonymous LDAP bind; (2) Public API directory listing. Which audit outcomes would directly demonstrate protection for those areas? Choose TWO.

  1. External clients receive time service as intended but cannot retrieve protected management details.
  2. Unauthenticated directory queries return no sensitive users, group membership, or privileged attributes.
  3. Tests with an unprivileged token cannot list restricted identifiers or fields.
  4. Unauthorized SNMP reads fail and approved SNMPv3 queries succeed with authenticated identities.
  5. Controlled mailbox probes cannot distinguish valid and invalid internal accounts from public responses.

Explanation

Correct Answers

B:

This verifies the anonymous LDAP bind component alongside anonymous LDAP bind in the combined audit: LDAP directory reads can disclose identity structure when anonymous search rights are too broad. For the anonymous LDAP bind audit set, the relevant observed case is that a directory service returns user and group details to an unauthenticated client connection.

C:

This verifies the public API directory listing component alongside anonymous LDAP bind in the combined audit: excessive API enumeration arises when list endpoints lack authorization or safe pagination and filtering. For the anonymous LDAP bind audit set, the relevant observed case is that an administrative API lists internal user identifiers through an endpoint open to all clients.

Incorrect Answers

A:

Some NTP management capabilities expose peer and status data unrelated to ordinary time service; this result is evidence about NTP management query when a time server responds to management requests with details beyond simple clock synchronization, not a direct closure test for the named anonymous LDAP bind, public API directory listing requirements.

D:

Legacy SNMP community strings act as weak shared access tokens, especially without encryption; this result is evidence about SNMP default communities when a network device exposes interface and configuration information through a shared default community string, not a direct closure test for the named anonymous LDAP bind, public API directory listing requirements.

E:

Recipient-verification responses can enable user-name discovery when they disclose account existence; this result is evidence about smtp recipient verification when a mail server confirms whether arbitrary mailbox names exist before a message is submitted, not a direct closure test for the named anonymous LDAP bind, public API directory listing requirements.

Question 364

The assessment lead requests a precise definition of digital signature authenticity. Which technical interpretation fits?

  1. An HMAC combines a secret key with a cryptographic hash to authenticate message integrity.
  2. Ephemeral key agreement can give forward secrecy by deriving session secrets independent of a recoverable long-term key.
  3. Signatures use a private signing key and are verified with the corresponding trusted public key.
  4. Public-key cryptography can use a recipient's public key to establish confidentiality while the private key stays secret.

Explanation

Correct Answer

C:

A software publisher wants recipients to verify who signed an update and whether its contents changed; that situation illustrates the actual operating behavior under review. Its practical safeguard is to sign releases through protected keys and verify signatures before applying updates, with confirmation when a modified update fails signature verification while the genuine signed artifact passes.

Incorrect Answers

A:

Two trusted systems share a secret and need to detect tampering in exchanged messages; those details characterize HMAC authentication and would call for protect HMAC keys and use a suitable modern hash with key separation, rather than explaining digital signature authenticity.

B:

A captured encrypted session should remain protected even if the server's long-term private key is exposed later; those details characterize TLS forward secrecy and would call for enable modern TLS suites with ephemeral key exchange and protect endpoint certificates, rather than explaining digital signature authenticity.

D:

A sender needs to protect a short secret for a recipient without first sharing a symmetric key; those details characterize asymmetric key roles and would call for validate recipient public keys and protect the associated private key from unauthorized use, rather than explaining digital signature authenticity.

Question 365

The team is closing an assessment finding: A database breach exposes password hashes rather than plaintext passwords or reversible encryption keys. What measure is most appropriate to implement?

  1. Store passwords with unique salts and a modern memory-hard or deliberately slow password hash.
  2. Detect cross-account failure patterns and enforce MFA with appropriate login throttling.
  3. Limit privileged logons, protect credentials, and isolate administrative access paths.
  4. Use narrowly scoped managed service identities with automated credential lifecycle management.

Explanation

Correct Answer

A:

Password hashing should use a slow, salted password KDF to resist offline guessing at scale; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that storage inspection shows distinct salts and an approved password hashing work factor for each account.

Incorrect Answers

B:

Password spraying distributes a small set of guesses across users to avoid rapid per-account lockout; the proposed safeguard addresses a case where authentication telemetry shows one guessed password attempted against many different accounts in a short interval, rather than the offline password hashing risk finding described here.

C:

Some Windows authentication paths can misuse credential-derived material without knowledge of the plaintext password; the proposed safeguard addresses a case where an administrator's reusable Windows authentication material is stolen from a workstation and later used elsewhere, rather than the offline password hashing risk finding described here.

D:

Long-lived shared privileged service credentials expand the blast radius of application compromise; the proposed safeguard addresses a case where an application service runs as a broadly privileged domain identity whose password never rotates, rather than the offline password hashing risk finding described here.

Question 366

An analyst is sorting findings by mechanism. One entry reads: An internet-connected camera can initiate sessions to corporate finance workstations. Which label is the right one?

  1. IoT network segregation
  2. IoT factory credentials
  3. Industrial DMZ separation
  4. Embedded web UI hardening

Explanation

Correct Answer

A:

Connected devices with limited management assurance should not inherit unrestricted enterprise network trust; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to place IoT devices in dedicated segments with narrowly permitted destination and management paths, verified when cross-segment tests show cameras cannot reach protected business hosts or administrative services.

Incorrect Answers

B:

Factory credentials create predictable management access if they remain active after device commissioning; this different classification would fit when multiple smart sensors share an unchanged default administrative password across an entire facility, not the evidence pointing to IoT network segregation in the question.

C:

An industrial DMZ mediates data exchange while reducing direct enterprise-to-control-system reachability; this different classification would fit when a historian sends process data to enterprise reporting systems through unrestricted two-way connections, not the evidence pointing to IoT network segregation in the question.

D:

Embedded management interfaces may retain obsolete defaults and limited authentication controls for years; this different classification would fit when a connected controller exposes a vendor maintenance page with unchanged factory settings over the plant network, not the evidence pointing to IoT network segregation in the question.

Question 367

During a sanctioned assessment the team observes: On a local IPv6 segment, devices identify neighbor link-layer addresses through ICMPv6 messages. Which next control or procedure best fits?

  1. Use route telemetry and approved traces together when analyzing an incomplete hop list.
  2. Interpret ICMP code and network path together instead of assuming every error means a dead host.
  3. Verify listener processes and application protocols rather than assigning services by port number alone.
  4. Protect router advertisements and neighbor discovery without indiscriminately blocking required ICMPv6.

Explanation

Correct Answer

D:

Neighbor Discovery replaces ARP for IPv6 and depends on ICMPv6 for local address resolution; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that a functional IPv6 test shows neighbor resolution succeeds while unauthorized router advertisements are rejected.

Incorrect Answers

A:

TTL or hop-limit expiry can elicit intermediate-router diagnostics without revealing every hidden segment; the proposed safeguard addresses a case where a path trace lists intermediate routers based on responses to packets with limited hop counts, rather than the IPv6 neighbor discovery finding described here.

B:

ICMP errors signal forwarding or delivery conditions and may be filtered or rate-limited in practice; the proposed safeguard addresses a case where a router returns a destination-unreachable diagnostic for a packet that cannot be forwarded, rather than the IPv6 neighbor discovery finding described here.

C:

Port numbers are conventions; application-layer content and process ownership establish actual service identity; the proposed safeguard addresses a case where a responder finds an HTTP-speaking service listening on an unexpected numeric port, rather than the IPv6 neighbor discovery finding described here.

Question 368

An approved test produces this finding: A document-preview service fetches an arbitrary URL supplied by a user and reaches internal-only resources. Which protective action most directly addresses it?

  1. Allowlist intended destinations and block internal or metadata network targets in the fetching service.
  2. Avoid native object deserialization from clients and use validated simple data contracts.
  3. Allowlist writable fields for each endpoint and enforce ownership and role restrictions.
  4. Check authorization on each privileged operation and deny unentitled roles server-side.

Explanation

Correct Answer

A:

SSRF abuses a server's network privileges to request destinations inaccessible to the external client; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that requests to prohibited internal destinations are rejected before any backend network connection.

Incorrect Answers

B:

Deserialization of untrusted object graphs can trigger unsafe code paths or unexpected property changes; the proposed safeguard addresses a case where an application reconstructs complex server objects directly from untrusted client-supplied serialized data, rather than the server-side request forgery finding described here.

C:

Mass assignment arises when untrusted request fields bind directly to sensitive model properties; the proposed safeguard addresses a case where a profile update API accepts an undocumented isAdmin property and writes it to the user record, rather than the server-side request forgery finding described here.

D:

Function authorization requires server-side role checks independent of hidden menus or client display logic; the proposed safeguard addresses a case where a regular user reaches an administrator-only action by directly calling its API route, rather than the server-side request forgery finding described here.

Question 369

The team is closing an assessment finding: A customer profile endpoint returns staff-only flags and internal identifiers even though the UI hides them. What measure is most appropriate to implement?

  1. Enforce per-object access policy for every data retrieval and modification request.
  2. Allowlist specific trusted origins and avoid wildcard or reflected credentialed origin permissions.
  3. Use role-aware server-side response schemas that expose only necessary authorized fields.
  4. Allowlist writable fields for each endpoint and enforce ownership and role restrictions.

Explanation

Correct Answer

C:

Sensitive fields remain exposed when authorization and output filtering occur only in the browser; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that API inspection confirms regular users receive no hidden privileged properties in JSON responses.

Incorrect Answers

A:

Object-level authorization fails when the server trusts a client-chosen identifier without checking ownership; the proposed safeguard addresses a case where a signed-in customer changes a record identifier and sees another customer's invoice, rather than the excessive API response data finding described here.

B:

Unsafe CORS policies may let untrusted websites read authenticated cross-origin responses in browsers; the proposed safeguard addresses a case where an API reflects arbitrary Origin headers while permitting browsers to include credentials in cross-origin requests, rather than the excessive API response data finding described here.

D:

Mass assignment arises when untrusted request fields bind directly to sensitive model properties; the proposed safeguard addresses a case where a profile update API accepts an undocumented isAdmin property and writes it to the user record, rather than the excessive API response data finding described here.

Question 370

The assessment lead requests a precise definition of exposed session cookie. Which technical interpretation fits?

  1. Client-side cookie deletion alone may not revoke server-recognized sessions or long-lived tokens.
  2. Failure to rotate session identifiers on privilege change can let a preselected identifier bind to an authenticated session.
  3. CSRF abuses ambient browser credentials when the application fails to verify the user's request intent.
  4. An accessible session token can be replayed to impersonate an authenticated browser session if stolen.
  5. SameSite controls when browsers attach cookies to cross-site requests, reducing some ambient-authentication abuse.

Explanation

Correct Answer

D:

A browser extension can read an authentication cookie because the cookie lacks appropriate client-side protections; that situation illustrates the actual operating behavior under review. Its practical safeguard is to protect session cookies with HttpOnly and Secure attributes and enforce TLS transport, with confirmation when browser inspection shows the session cookie is not script-readable and is sent only over HTTPS.

Incorrect Answers

A:

A user clicks logout, but a copied access token continues authorizing API requests until its original expiry; those details characterize session logout invalidation and would call for invalidate server-side session state and revoke relevant refresh tokens on logout, rather than explaining exposed session cookie.

B:

A user keeps the same session identifier after authentication that was assigned before login; those details characterize session fixation and would call for regenerate the session identifier after successful login or privilege elevation, rather than explaining exposed session cookie.

C:

A logged-in user's browser submits a state-changing request after visiting an unrelated malicious page; those details characterize cross-site request forgery and would call for use anti-CSRF tokens and suitable SameSite cookie restrictions on state-changing operations, rather than explaining exposed session cookie.

E:

A cross-site navigation unexpectedly includes a privileged session cookie in a request to an internal application; those details characterize sensitive cookie samesite policy and would call for choose an appropriate SameSite policy and independently protect state-changing requests against CSRF, rather than explaining exposed session cookie.

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