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.

• ✗

  Cross-Site Request Forgery (CSRF)

  Why it's wrong here

  Cross-Site Request Forgery (CSRF) exploits a user's authenticated session to trick their browser into sending an unintended, malicious request to a vulnerable web application. While a WebDAV client *could* be targeted by CSRF if it were a browser-based application, the mere enabling of the WebDAV protocol on an IIS server does not inherently introduce a CSRF vulnerability within the WebDAV service itself. The primary risk associated with WebDAV is direct server interaction, not coercing a user's browser.

• ✗

  SQL injection

  Why it's wrong here

  SQL injection vulnerabilities arise when an application constructs SQL queries using unsanitized user input, allowing an attacker to manipulate database commands. WebDAV, as a protocol for managing files and directories on a web server, does not directly interact with SQL databases in its core functionality. Therefore, enabling WebDAV on IIS does not introduce a SQL injection vulnerability; it operates at a different layer of the application stack, independent of database query processing.

• ✓

  File upload leading to remote code execution

  Why this is correct

  WebDAV provides HTTP methods like PUT and MKCOL, enabling clients to upload and manage files on the server. If WebDAV is enabled with write permissions and the server is misconfigured to allow execution of uploaded files (e.g., ASP, ASPX, PHP, or even compiled executables) within a web-accessible directory, an attacker can upload a malicious web shell or other executable code. Subsequently accessing this uploaded file through the web server will trigger its execution, granting the attacker remote code execution capabilities on the server.

• ✗

  Directory traversal

  Why it's wrong here

  Directory traversal, or path traversal, allows an attacker to access files and directories outside the intended web root by manipulating file paths, typically using ".." sequences. This vulnerability primarily focuses on *reading* or *accessing* unauthorized files on the server's file system. While an attacker might use WebDAV to enumerate directories, the core risk of WebDAV with write permissions is the ability to *upload* or *modify* files, which is distinct from merely traversing and reading existing files.

Go deeper

Related to this question