Sanitizer boundary: Input reaches LDAP query grammar and can alter the directory search.
The pack does not provide a callable signature for this record; the watched access path is shown directly.
| Arg | Access path | Purpose | Watched |
|---|---|---|---|
| Argument[0] | Argument[0] | The access path Atropos marks for this model. | ▲ sanitizer |
Attacker's-eye view · ldap-injection
Special LDAP characters change the filter or distinguished name and broaden or redirect the query.
// modeled boundary: Argument[0] -> ReturnValue
escape_filter_chars(attacker_influenced_value);
1Use the library's escaping or parameter API.
2Keep filter structure fixed.
3Validate identifiers for their expected domain.
These checks require the surrounding codebase. The model names the boundary; it does not decide reachability or prove that a guard dominates every path.
Is this a bug in your code?Atropos stops here — by design
Atropos identifies Argument[0] -> ReturnValue as a ldap-injection sanitizer. It cannot see whether untrusted data reaches this call in your repository.
Lachesis is the codebase-level step: it traces reachability and guards for this symbol.
Check this symbol in Lachesis →Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| sanitizer | ldap-injection | Argument[0] -> ReturnValue | python.ldap.filter.escapefilterchars.a0-ret | high · corrob. 2 |