Sink boundary: A TLS or certificate operation is modeled because it controls whether a remote peer is trusted.
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.
CWE-295 ↗
Improper Certificate Validation
A certificate is not validated correctly before it is trusted.
Attacker's-eye view · insecure-tls
Weak validation or configuration lets an attacker impersonate the intended endpoint.
// modeled boundary: ReturnValue
_create_unverified_context(attacker_influenced_value);
1Validate the certificate chain and hostname.
2Use current protocols and algorithms.
3Do not disable verification for convenience.
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 insecure-tls 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 →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 |
|---|---|---|---|---|
| sink | insecure-tls | ReturnValue | python.ssl.createunverifiedcontext.ret | medium · corrob. 2 |