Source boundary: An archive entry is modeled because its name or contents can cross a filesystem boundary.
The pack does not provide a callable signature for this record; the watched access path is shown directly.
No positional argument is specified; inspect the return value or named access path in the model facts below.
Attacker's-eye view · archive-entry
A crafted archive member uses traversal or link behavior to write outside the intended extraction directory.
// modeled boundary: ReturnValue
getmembers(attacker_influenced_value);
1Normalize and validate the entry path.
2Reject traversal and unexpected links.
3Extract with least privilege into an isolated directory.
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 ReturnValue as a archive-entry source. 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
●namelistpythonWhat neutralizes it
No sanitizer of this kind is modeled.
Model facts · verbatim from the pack
| Role | Kind | Access path | Model ID | Confidence |
|---|---|---|---|---|
| source | archive-entry | ReturnValue | python.archive.getmembers.ret | medium · corrob. 2 |