During a security assessment, a tester finds that a web application accepts user input and directly uses it in an LDAP query without sanitization. Which of the following attacks is most likely to be successful?
Trap 1: Cross-site scripting
Unsynchronised input in an LDAP filter enables LDAP injection, letting attackers alter query logic to bypass authentication or enumerate directory entries; cross-site scripting targets browser output, not directory queries. XSS is tempting because it is the classic injection answer for unsanitised input, but the sink here is an LDAP query.
Trap 2: SQL injection
SQL injection targets SQL database parsers, but the sink here is an LDAP directory query, so injected metacharacters manipulate directory filters rather than SQL statements. It is tempting because both are injection flaws from unsanitised input, yet the interpreter and syntax differ, making LDAP injection the actual risk.
Trap 3: Remote file inclusion
Remote file inclusion requires a file-inclusion function that fetches external URLs, typically via a path or URL parameter; an LDAP query sink cannot include remote files. It is tempting as another injection-class flaw, but the mechanism — loading attacker-hosted code — is absent from this directory-query context.
- A
Cross-site scripting
Why it fails: Unsynchronised input in an LDAP filter enables LDAP injection, letting attackers alter query logic to bypass authentication or enumerate directory entries; cross-site scripting targets browser output, not directory queries. XSS is tempting because it is the classic injection answer for unsanitised input, but the sink here is an LDAP query.
- B
SQL injection
Why it fails: SQL injection targets SQL database parsers, but the sink here is an LDAP directory query, so injected metacharacters manipulate directory filters rather than SQL statements. It is tempting because both are injection flaws from unsanitised input, yet the interpreter and syntax differ, making LDAP injection the actual risk.
- C
Remote file inclusion
Why it fails: Remote file inclusion requires a file-inclusion function that fetches external URLs, typically via a path or URL parameter; an LDAP query sink cannot include remote files. It is tempting as another injection-class flaw, but the mechanism — loading attacker-hosted code — is absent from this directory-query context.
- D
LDAP injection
Unsanitised input concatenated into an LDAP filter lets the tester alter query logic, so LDAP injection succeeds. The stem's constraint is direct use of user input in an LDAP query without sanitisation, which this attack specifically exploits.