Attacker-controlled rollback restores a prohibited security state
An attacker bypasses an update version authorization policy to cause a rollback that restores a prohibited security state.
Candidate CWE: CWE-863
Test hypothesis#
In a local update fixture, compare current and older authentic versions under unchanged verifier policy. Show how the attacker supplies the older artifact without signing or administrative authority.
Evidence required#
Rollback policy, exact versions, artifact authenticity, attacker control and the concrete restored security consequence.
Rule out false positives#
Supported manual downgrade, administrator-selected rollback, or older-version installation alone is insufficient. Explicit ADB downgrade flags do not demonstrate a bypass. Select the final CWE from the demonstrated root cause; algorithm negotiation and hardware security-version CWEs do not automatically apply.
Playbook and command references#
- Update signatures, rollback and privileged installation — Test the update decision and installation boundary while preserving production signer and privilege assumptions.
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.