Nombre: Security Version Number Mutable to Older Versions

The security version number in the hardware product is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.

Informaciones generales

Detalles de contexto

Modos de introducción

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.

Plataformas aplicables

Lenguaje

Clase: Not Language-Specific (Undetermined)

Sistemas operativos

Clase: Not OS-Specific (Undetermined)

Arquitecturas

Clase: Not Architecture-Specific (Undetermined)

Tecnologías

Nombre: Security Hardware (Undetermined)
Clase: Not Technology-Specific (Undetermined)

Consecuencias comunes

Alcance	Impacto	Probabilidad
Confidentiality Integrity Authentication Authorization	Other, Alter Execution Logic, Unexpected State Note: 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 Note: An adversary could prevent upgrades, casing a denial of service.

Mitigaciones potenciales

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.

Métodos de detección

Automated Dynamic Analysis

Mutability of stored security version numbers and programming with older firmware images should be part of automated testing.
Efectividad : High

Architecture or Design Review

Anti-roll-back features should be reviewed as part of Architecture or Design review.
Efectividad : High

Notas de mapeo de vulnerabilidades

Justificación : 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.
Comentario : 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.

Patrones de ataque relacionados

CAPEC ID	Nombre del patrón de ataque
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.

Envío

Nombre	Organización	Fecha	Fecha de lanzamiento	Version
Arun Kanuparthi, Hareesh Khattri, Parbati Kumar Manna	Intel Corporation	2020-04-25 +00:00	2020-12-10 +00:00	4.3

Modificaciones

Nombre	Organización	Fecha	Comentario
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

Detalle CWE-1328

CWE-1328