Summary boundary: An alias carries data into another modeled access path; the security meaning depends on what receives it.
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. | ▲ summary |
No CWE mapping in this fact
The model classifies the behavior as alias; no CWE relationship is attached to this record.
Attacker's-eye view · alias
An attacker supplies a value at the source and it remains attached as it crosses the alias into a later operation.
// modeled boundary: Argument[0] -> ReturnValue
memchr(attacker_influenced_value);
1Identify the value that is aliased.
2Trace every consumer of the alias.
3Check whether a later boundary constrains it.
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 alias summary. 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 |
|---|---|---|---|---|
| summary | alias | Argument[0] -> ReturnValue | c.std.memchr.a0-ret | high · corrob. 3 |