Read Time:1 Minute, 35 Second
Description
A device’s real time power consumption may be monitored during security token evaluation and the information gleaned may be used to determine the value of the reference token.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
CWE-1300
CWE-1259
Consequences
Confidentiality, Integrity, Availability, Access Control, Accountability, Authentication, Authorization, Non-Repudiation: Modify Memory, Read Memory, Read Files or Directories, Modify Files or Directories, Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity, Bypass Protection Mechanism, Read Application Data, Modify Application Data, Hide Activities
As compromising a security token may result in complete system control, the impacts are relatively universal
Potential Mitigations
Phase: Architecture and Design
Description:
The design phase must consider each check of a security token against a standard and the amount of power consumed during the check of a good token versus a bad token. The alternative is an all at once check where a retry counter is incremented PRIOR to the check.
Phase: Architecture and Design
Description:
Another potential mitigation is to parallelize shifting of secret data (see example 2 below). Note that the wider the bus the more effective the result.
Phase: Architecture and Design
Description:
An additional potential mitigation is to add random data to each crypto operation then subtract it out afterwards. This is highly effective but costly in performance, area, and power consumption. It also requires a random number generator.
Phase: Implementation
Description:
If the architecture is unable to prevent the attack, using filtering components may reduce the ability to implement an attack, however, consideration must be given to the physical removal of the filter elements.
Phase: Integration
Description:
During integration, avoid use of a single secret for an extended period (e.g. frequent key updates). This limits the amount of data compromised but at the cost of complexity of use.
CVE References
- CVE-2020-12788
- CMAC verification vulnerable to timing and power attacks.
