getpw

c · standard library
sinkDerived from model facts
RoleSink
WeaknessCWE-120 · CWE-676 · CWE-787
WatchesArgument[1]
Kindbuffer-write
Confidencemedium
Corroboration1

Sink boundary: A write operation reaches a buffer without carrying an inherent proof that the destination is large enough.

Argument map · what each slot does

The pack does not provide a callable signature for this record; the watched access path is shown directly.

ArgAccess pathPurposeWatched
Argument[1]Argument[1]The access path Atropos marks for this model.▲ sink
The weakness
CWE-120
Classic Buffer Overflow

Input is copied into an output buffer without checking that it fits.

CWE-676
Potentially Dangerous Function

A function can introduce a vulnerability when used without its required constraints.

CWE-787
Out-of-bounds Write

Data is written past the end or before the beginning of its intended buffer.

What goes wrong
Attacker's-eye view · buffer-write

Input longer than the destination overwrites adjacent memory or truncates unexpectedly.

// modeled boundary: Argument[1] getpw(attacker_influenced_value);
To decide if this call is a bug, check
1Identify destination capacity.
2Check the write length before the call.
3Confirm truncation or rejection is explicit.
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[1] as a buffer-write 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
The family · buffer-write

Across languages

No cross-language match.

What neutralizes it

No sanitizer of this kind is modeled.

Model facts · verbatim from the pack
RoleKindAccess pathModel IDConfidence
sinkbuffer-writeArgument[1]c.std.getpw.a1medium · corrob. 1