CWE-1232
Weakness AllowedImproper Lock Behavior After Power State Transition
Abstraction: Base · Status: Incomplete
Register lock bit protection disables changes to system configuration once the bit is set. Some of the protected registers or lock bits become programmable after power state transitions (e.g., Entry and wake from low power sleep modes) causing the system configuration to be changeable.
Technical nuance
Some common weaknesses that can exist in such a protection scheme are that the lock gets cleared, the values of the protected registers get reset, or the lock become programmable.
Mapping guidance
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
Content history
suggested demonstrative example
suggested demonstrative example
updated Common_Consequences, Demonstrative_Examples, Description, Modes_of_Introduction, Potential_Mitigations, Related_Attack_Patterns
updated Description
updated Relationships
updated Mapping_Notes
updated Demonstrative_Examples, References
updated Weakness_Ordinalities
updated Background_Details, Demonstrative_Examples, Description, Technical_Nuance
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
Mitigation
- Security Lock bit protections should be reviewed for behavior across supported power state transitions.
- Security lock programming flow and lock properties should be tested in pre-silicon and post-silicon testing including testing across power transitions.
CAPEC-166: Force the System to Reset Values
An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions.