CS0-003 Vulnerability Management 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.

• ✓

  SQL injection

  Why this is correct

  SQL injection is an injection flaw that occurs when untrusted data is directly concatenated into SQL queries, allowing attackers to manipulate database logic. For example, an attacker can submit a value like `' OR '1'='1` to bypass authentication or extract sensitive data. This happens because user input is not parameterized or properly sanitized before being sent to the database interpreter.

• ✓

  OS command injection

  Why this is correct

  OS command injection is an injection flaw that allows an attacker to execute arbitrary operating system commands on the server by injecting command syntax through application inputs. This typically occurs when input is passed to shell execution functions like `system()` or `exec()` without proper validation or escaping. An attacker might append `; rm -rf /` or `| whoami` to a parameter, causing the application to unintentionally run those commands.

• ✗

  Broken Access Control

  Why it's wrong here

  Broken Access Control is a separate vulnerability category, not an injection flaw. It arises when an application fails to enforce restrictions on what authenticated users can access or do, such as viewing other users' private data or performing unauthorized functions. Unlike injection attacks, it does not involve sending malicious interpretable code; instead, it relies on manipulating requests, URLs, or client-side state to bypass authorization checks.

• ✓

  Cross-Site Scripting (XSS)

  Why this is correct

  Cross-Site Scripting (XSS) is a type of injection attack where an attacker injects malicious client-side scripts, often JavaScript, into web pages that are then viewed by other users. This occurs when user input is embedded in HTML output without proper encoding, allowing the script to execute in a victim's browser. XSS is an injection flaw because untrusted data is sent to the HTML/JavaScript interpreter, but it targets the client side rather than server-side databases or shells.

• ✗

  Security Misconfiguration

  Why it's wrong here

  Security Misconfiguration is a separate vulnerability category and not an injection flaw. It results from insecure default configurations, incomplete setups, open cloud storage, verbose error messages, or unnecessary enabled features. This category does not involve injecting malicious input into an interpreter; rather, it happens because the application or its environment is not securely configured, leaving doors open for various types of attacks.

Go deeper

Related to this question