Firmware security-version state can be lowered
An attacker can reduce the protected security version and thereby restore software excluded by the anti-rollback policy.
Candidate CWE: CWE-1328
Test hypothesis#
In a local model or recoverable bench fixture, compare an authentic current image and older signed security version. Trace whether the eligible caller can lower the counter or select a bypass path.
Evidence required#
Security counter before/after, downgrade policy, signed image versions, caller access and reinstated vulnerable security state.
Rule out false positives#
Normal application rollback after failed boot validation, lower marketing versions and explicitly permitted recovery are distinct from anti-rollback bypass.
Playbook and command references#
- Firmware update and boot trust: signed bytes, product binding and rollback — Separate download trust, update authorization, image verification, rollback policy and boot enforcement using local artifacts.
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.