Sink boundary: Input reaches XPath expression grammar and can change the selected XML data.
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. | ▲ sink |
Attacker's-eye view · xpath-injection
A crafted predicate broadens, bypasses, or redirects the XML query.
// modeled boundary: Argument[0]
XPath(attacker_influenced_value);
1Use parameterized XPath APIs where available.
2Keep expression structure fixed.
3Escape and validate values for the XPath context.
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] as a xpath-injection sink. 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
●xmlXPathCompilec●xmlXPathEvalc●xmlXPathEvalExpressionc●selectjavascript●xpathpython●findpythonAcross languages
●xmlXPathCompilec●xmlXPathEvalc●xmlXPathEvalExpressionc●selectjavascript●selecttypescriptWhat neutralizes it
No sanitizer of this kind is modeled.
Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| sink | xpath-injection | Argument[0] | python.lxml.etree.xpath.a0 | high · corrob. 2 |