Race condition in a security-sensitive transition
Concurrent operations violate a rule that holds when the same actions run serially.
Candidate CWE: CWE-362
Test hypothesis#
Use a fresh nonfinancial fixture. Complete a normal serial/replay control, reset it, then submit two bounded simultaneous operations. Inspect durable state after both requests and workers finish.
Evidence required#
A duplicate membership, resource, or synthetic state transition persists. Include the invariant, initial state, serial control, concurrency mechanism, and committed result.
Rule out false positives#
Two 200 responses, transient UI counters, expected retries, or no verified timing overlap do not prove or disprove a race.
Playbook and command references#
- Workflow invariants, replay, idempotency, and races — Find security consequences in workflow ordering and concurrency, with serial controls and durable-state evidence.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.