Sposoby wprowadzenia
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.
Odpowiednie platformy
Język
Class: Not Language-Specific (Undetermined)
Systemy operacyjne
Class: Not OS-Specific (Undetermined)
Architektury
Class: Not Architecture-Specific (Undetermined)
Technologie
Name: Security Hardware (Undetermined)
Class: Not Technology-Specific (Undetermined)
Typowe konsekwencje
| Zakres |
Wpływ |
Prawdopodobieństwo |
Confidentiality Integrity Authentication Authorization | Other
Note: Impact includes roll-back or downgrade to a vulnerable version of the firmware or DoS (prevent upgrades). | High |
Potencjalne środki zaradcze
Phases : Architecture and Design
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.
Metody wykrywania
Automated Dynamic Analysis
Mutability of stored security version numbers and programming with older firmware images should be part of automated testing.
Skuteczność : High
Architecture or Design Review
Anti-roll-back features should be reviewed as part of Architecture or Design review.
Skuteczność : High
Uwagi dotyczące mapowania podatności
Uzasadnienie : 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.
Komentarz : 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.
Powiązane wzorce ataków
| CAPEC-ID |
Nazwa wzorca ataku |
| 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. |
Zgłoszenie
| Nazwa |
Organizacja |
Data |
Data wydania |
Version |
| Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna |
Intel Corporation |
2020-04-25 +00:00 |
2020-12-10 +00:00 |
4.3 |
Modyfikacje
| Nazwa |
Organizacja |
Data |
Komentarz |
| 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 |