CEH Web Application and Injection Attacks Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Reflected Cross-Site Scripting (XSS)

  Why it's wrong here

  Reflected Cross-Site Scripting (XSS) involves injecting unvalidated user input containing malicious scripts directly into the HTTP response, which is then executed by the victim's browser. This client-side vulnerability aims to steal cookies, deface content, or redirect users. However, it does not directly involve manipulating server-side object identifiers in URLs to bypass authorization checks for different resources or access unauthorized data.

• ✗

  Command Injection

  Why it's wrong here

  Command Injection exploits vulnerabilities where user-supplied input is directly incorporated into operating system commands executed by the application. This allows an attacker to run arbitrary system commands on the server, potentially gaining control or accessing sensitive files from the underlying system. It does not directly relate to manipulating application-specific object IDs within a URL to access unauthorized data, but rather targets the server's operating system shell.

• ✗

  Cross-Site Request Forgery (CSRF)

  Why it's wrong here

  Cross-Site Request Forgery (CSRF) tricks an authenticated user into unknowingly executing unwanted actions on a web application where they are currently logged in. This attack leverages the user's existing session and trust in the site, forcing their browser to send a forged request to perform actions like changing passwords or making purchases. Unlike IDOR, CSRF does not involve an attacker directly manipulating object references in a URL to bypass authorization and access another user's data; instead, it coerces the legitimate user to perform actions on their *own* behalf.

• ✓

  Insecure Direct Object Reference (IDOR)

  Why this is correct

  Insecure Direct Object Reference (IDOR) occurs when an application exposes a direct reference to an internal implementation object, such as a file, database key, or directory, and fails to implement proper authorization checks. An attacker can manipulate these references, often found in URL parameters, form fields, or API requests, to access or modify resources belonging to other users or unauthorized data. This vulnerability directly exploits the application's trust in user-supplied object identifiers without verifying the user's permission to access that specific object, leading to unauthorized information disclosure or modification.

Go deeper

Related to this question