Modos de Introdução
Architecture and Design : The design of the algorithm itself may intrinsically allow the power side channel attack to be effective.
Implementation : This weakness may be introduced during implementation despite a robust design that otherwise prevents exploitation.
Plataformas Aplicáveis
Linguagem
Class: Not Language-Specific (Undetermined)
Sistemas Operacionais
Class: Not OS-Specific (Undetermined)
Arquiteturas
Class: Not Architecture-Specific (Undetermined)
Tecnologias
Class: Not Technology-Specific (Undetermined)
Consequências Comuns
| Escopo |
Impacto |
Probabilidade |
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
Note: As compromising a security token may result in complete system control, the impacts are relatively universal. | |
Exemplos Observados
| Referências |
Descrição |
| CMAC verification vulnerable to timing and power attacks. |
Mitigações Potenciais
Phases : Architecture and Design
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.
Phases : Architecture and Design
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.
Phases : Architecture and Design
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.
Phases : Implementation
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.
Phases : Integration
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.
Notas de Mapeamento de Vulnerabilidade
Justificativa : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Comentário : 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.
Padrões de Ataque Relacionados
| CAPEC-ID |
Nome do Padrão de Ataque |
| CAPEC-189 |
Black Box Reverse Engineering
An adversary discovers the structure, function, and composition of a type of computer software through black box analysis techniques. 'Black Box' methods involve interacting with the software indirectly, in the absence of direct access to the executable object. Such analysis typically involves interacting with the software at the boundaries of where the software interfaces with a larger execution environment, such as input-output vectors, libraries, or APIs. Black Box Reverse Engineering also refers to gathering physical side effects of a hardware device, such as electromagnetic radiation or sounds. |
Referências
REF-1184
Power Analysis
Wikipedia.
https://en.wikipedia.org/wiki/Power_analysis
Submissão
| Nome |
Organização |
Data |
Data de lançamento |
Version |
| CWE Content Team |
MITRE |
2020-05-29 +00:00 |
2020-08-20 +00:00 |
4.2 |
Modificações
| Nome |
Organização |
Data |
Comentário |
| CWE Content Team |
MITRE |
2021-03-15 +00:00 |
updated Functional_Areas, Maintenance_Notes, Relationships |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Demonstrative_Examples, Modes_of_Introduction, Observed_Examples, Potential_Mitigations, References, Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Maintenance_Notes, References, Relationships, Type |
| CWE Content Team |
MITRE |
2022-06-28 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2022-10-13 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2024-02-29 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |