背景詳情
引入方式
Architecture and Design
Implementation : Such issues could be introduced during hardware architecture and design, and can be identified later during testing or system configuration phases.
適用平台
程式語言
類別: Not Language-Specific (Undetermined)
作業系統
類別: Not OS-Specific (Undetermined)
架構
類別: Not Architecture-Specific (Undetermined)
技術
名稱: Security Hardware (Undetermined)
類別: Not Technology-Specific (Undetermined)
常見後果
| 範圍 |
影響 |
可能性 |
Confidentiality Integrity Authentication Authorization | Other, Alter Execution Logic, Unexpected State
注意:If the security version number is modifiable by an adversary, this allows attacks like downgrading to a previous version that contains vulnerabilities. Once downgraded to a previous version, an adversary can launch exploits on the SoC and thus compromise the security of the SoC. These downgrade attacks are also referred to as roll-back attacks. | High |
| Availability | Other, Alter Execution Logic, Unexpected State
注意:An adversary could prevent upgrades, casing a denial of service. | |
潛在緩解措施
Phases : Architecture and Design
The security version number must be stored securely and persistently across power-on resets. When architecting the system, security version data should be designated for storage in registers that are either read-only or have access controls that prevent modification by an untrusted agent.
Phases : Implementation
During implementation and test, security version data should be demonstrated to be read-only and access controls should be validated.
偵測方法
Automated Dynamic Analysis
Mutability of stored security version numbers and programming with older firmware images should be part of automated testing.
有效性 : High
Architecture or Design Review
Anti-roll-back features should be reviewed as part of Architecture or Design review.
有效性 : High
漏洞對應備注
理由說明 : 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.
相關攻擊模式
| CAPEC ID |
攻擊模式名稱 |
| CAPEC-176 |
Configuration/Environment Manipulation
An attacker manipulates files or settings external to a target application which affect the behavior of that application. For example, many applications use external configuration files and libraries - modification of these entities or otherwise affecting the application's ability to use them would constitute a configuration/environment manipulation attack. |
提交
| 名稱 |
機構 |
日期 |
發布日期 |
Version |
| Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna |
Intel Corporation |
2020-04-25 +00:00 |
2020-12-10 +00:00 |
4.3 |
修改記錄
| 名稱 |
機構 |
日期 |
備註 |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Related_Attack_Patterns |
| CWE Content Team |
MITRE |
2021-10-28 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2022-04-28 +00:00 |
updated Applicable_Platforms |
| CWE Content Team |
MITRE |
2022-06-28 +00:00 |
updated Applicable_Platforms |
| 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 |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description, Potential_Mitigations |