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.

• ✓

  An attacker tricks the server into making requests to internal or external resources

  Why this is correct

  Server-Side Request Forgery (SSRF) occurs when an attacker exploits a vulnerability in a web application to compel the server itself to make arbitrary requests. These requests can target internal network resources, such as other services, databases, or cloud metadata APIs, which are typically inaccessible directly from the internet. The server acts as a proxy, fetching data or performing actions on behalf of the attacker, often bypassing firewall rules and network segmentation. This allows for reconnaissance, port scanning, and even direct interaction with sensitive internal systems.

• ✗

  An attacker sends a malicious script that executes in a user's browser

  Why it's wrong here

  This describes Cross-Site Scripting (XSS), a client-side vulnerability where an attacker injects malicious scripts, typically JavaScript, into web pages viewed by other users. When a victim's browser loads the compromised page, the injected script executes within their browser's security context, allowing the attacker to steal session cookies, deface websites, redirect users, or perform actions on the user's behalf. XSS attacks specifically target the end-user's browser, not the server's ability to make requests.

• ✗

  An attacker forges HTTP requests to perform actions on behalf of an authenticated user

  Why it's wrong here

  This scenario accurately describes Cross-Site Request Forgery (CSRF). In a CSRF attack, an attacker crafts a malicious web page or email that, when loaded by an authenticated user, forces their browser to send an unwanted request to a trusted web application. Because the user is already authenticated with the target site, the forged request includes their session cookies, making it appear legitimate to the server and allowing the attacker to perform actions like changing passwords or transferring funds without the user's explicit consent.

• ✗

  An attacker injects SQL commands into a database query

  Why it's wrong here

  This is a classic description of SQL Injection (SQLi). SQLi occurs when an attacker exploits vulnerabilities in an application's input fields to insert malicious SQL code into a database query. This manipulation allows the attacker to bypass authentication, retrieve sensitive data from the database, modify or delete existing data, or even execute administrative commands on the database server. Unlike SSRF, SQLi directly targets the database layer through application input, not the server's outbound request capabilities.

Go deeper

Related to this question