CWE-1272: Sensitive Information Uncleared Before Debug/Power State Transition

How it's found

Sensitive Information Uncleared Before Debug/Power State Transition is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.

A device or system frequently employs many power and sleep states during its normal operation (e.g., normal power, additional power, low power, hibernate, deep sleep, etc.). A device also may be operating within a debug condition. State transitions can happen from one power or debug state to another. If there is information available in the previous state which should not be available in the next state and is not properly removed before the transition into the next state, sensitive information may leak from the system.

Vulnerable vs. safe

During the transition from A to B, the device does not scrub the memory.

For transition from state A to state B, remove information which should not be available once the transition is complete.

Consequences

• Read Memory, Read Application Data: Sensitive information may be used to unlock additional capabilities of the device and take advantage of hidden functionalities which could be used to compromise device security.

Mitigations

• Architecture and Design/Implementation: During state transitions, information not needed in the next state should be removed before the transition to the next state.

Where this fits in a TurboPentest engagement

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.

Frequently asked questions

Related CWEs

• Base weakness
  CWE-226: Sensitive Information in Resource Not Removed Before Reuse