Sanitizer boundary: A regular expression defines an input boundary whose accepted language may be broader than intended.
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 |
CWE-625 ↗
Permissive Regular Expression
A regular expression accepts a broader set of values than intended.
Attacker's-eye view · regex
A crafted value matches an overly permissive pattern and reaches a later sensitive operation.
// modeled boundary: Argument[0] -> ReturnValue
escape(attacker_influenced_value);
1Test positive and negative boundary cases.
2Anchor the pattern when matching whole values.
3Apply a domain-specific parser where possible.
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 regex 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 →Same behavior
No sibling records in this pack.
Across languages
No cross-language match.
What neutralizes it
No sanitizer of this kind is modeled.
Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| sanitizer | regex | Argument[0] -> ReturnValue | python.re.escape.a0-ret | low · corrob. 1 |