The product uses a broken or weak cryptographic primitive.
Use current, vetted primitives (AES-GCM, SHA-256+, Argon2); never build custom crypto.
MITRE ATT&CK techniques associated with this weakness class (mapped via MITRE CAPEC). A vulnerability of this type could let an adversary carry out:
A stage-by-stage walkthrough of the attack, mapped to the real MITRE ATT&CK tactics for this weakness — what the attacker is trying to do, what's at risk (what can be stolen or damaged), and how you defend. Understanding the playbook is how you shut it down.
Use the weakness as the way in — the first foothold on the system.
The vulnerable entry point (an input, endpoint, or dependency) that accepts attacker-controlled data.
Validate and sanitise all input at the boundary; patch to a fixed version.
Steal passwords, tokens, keys, and session material.
Passwords, API keys, session tokens, SSH/TLS keys, and secrets in memory, env, or config.
Secret managers, short-lived tokens, and no secrets in code/env/logs.
This is a defensive, conceptual walkthrough for education — stages reflect MITRE ATT&CK tactics associated with this weakness class, not a working exploit. Not every attack uses every stage.