# Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') (CWE-90)

The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query.

**Stack:** Go

- Prevalence: High Frequently exploited
- Impact: High 3 high-severity rules
- Prevention: Documented 3 fix examples

**OWASP:** Injection (A03:2021-Injection) - #3

## Description

If user input is incorporated into an LDAP query without proper sanitization, an attacker can inject LDAP commands that could read or modify sensitive directory information.

## Prevention

Prevention strategies for LDAP Injection based on 1 Shoulder detection rules.

### Go

Use ldap.EscapeFilter to sanitize user input in LDAP queries

## Warning Signs

- [HIGH] user input flowing to LDAP queries without proper escaping

## Consequences

- Read Application Data
- Modify Application Data
- Bypass Protection Mechanism

## Mitigations

- Use parameterized LDAP queries where possible
- Escape or encode all user input used in LDAP queries
- Validate input against an allowlist of acceptable characters

## Detection

- Total rules: 3
- Languages: go, javascript, typescript, python

## Rules by Language

### Go (1 rules)

- **LDAP Injection** [HIGH]: Detects user input flowing to LDAP queries without proper escaping.
  - Remediation: Use ldap.EscapeFilter to sanitize user input before including in LDAP filters.

```go
escaped := ldap.EscapeFilter(username)
filter := fmt.Sprintf("(uid=%s)", escaped)
```

Learn more: https://shoulder.dev/learn/go/cwe-90/ldap-injection