Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-1243 Base Incompleto
Sensitive Non-Volatile Information Not Protected During Debug
This vulnerability occurs when security-critical data stored in hardware fuses is left unprotected and accessible during debug modes.
Definição
What is CWE-1243?
This vulnerability occurs when security-critical data stored in hardware fuses is left unprotected and accessible during debug modes.
Modern chips store highly sensitive data—like encryption keys, root secrets, and unique manufacturer codes—in permanent hardware fuses. When the device powers on, this information is loaded into temporary registers or on-chip memory for runtime use. While normal software access to these locations is usually restricted, debug interfaces often bypass these protections entirely.
During debug or testing operations, these temporary storage locations remain exposed, allowing anyone with debug access to read the sensitive fuse data. This creates a significant hardware-level security gap, as an attacker can extract foundational secrets that underpin the device's entire security model, potentially compromising encryption, authentication, and secure boot processes.
Impacto no mundo real
Real-world CVEs caused by CWE-1243
Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Sensitive manufacturing data (such as die information) are stored in fuses. When the chip powers on, these values are read from the fuses and stored in microarchitectural registers. These registers are only given read access to trusted software running on the core. Untrusted software running on the core is not allowed to access these registers.
- 2
The example code below is taken from one of the AES cryptographic accelerators of the HACK@DAC'21 buggy OpenPiton SoC [REF-1366]. The operating system (OS) uses three AES keys to encrypt and decrypt sensitive data using this accelerator. These keys are sensitive data stored in fuses. The security of the OS will be compromised if any of these AES keys are leaked. During system bootup, these AES keys are sensed from fuses and stored in temporary hardware registers of the AES peripheral. Access to these temporary registers is disconnected during the debug state to prevent them from leaking through debug access. In this example (see the vulnerable code source), the registers key0, key1, and key2 are used to store the three AES keys (which are accessed through key_big0, key_big1, and key_big2 signals). The OS selects one of these three keys through the key_big signal, which is used by the AES engine.
- 3
The above code illustrates an instance of a vulnerable implementation for blocking AES key mechanism when the system is in debug mode (i.e., when debug_mode_i is asserted). During debug mode, key accesses through key_big0 and key_big1 are effectively disconnected, as their values are set to zero. However, the key accessed via the key_big2 signal remains accessible, creating a potential pathway for sensitive fuse data leakage, specifically AES key2, during debug mode. Furthermore, even though it is not strictly necessary to disconnect the key_big signal when entering debug mode (since disconnecting key_big0, key_big1, and key_big2 will inherently disconnect key_big), it is advisable, in line with the defense-in-depth strategy, to also sever the connection to key_big. This additional security measure adds an extra layer of protection and safeguards the AES keys against potential future modifications to the key_big logic.
- 4
To mitigate this, disconnect access through key_big2 and key_big during debug mode [REF-1367].
Exemplo de código vulnerável
Vulnerable Other
Sensitive manufacturing data (such as die information) are stored in fuses. When the chip powers on, these values are read from the fuses and stored in microarchitectural registers. These registers are only given read access to trusted software running on the core. Untrusted software running on the core is not allowed to access these registers.
All microarchitectural registers in this chip can be accessed through the debug interface. As a result, even an untrusted debugger can access this data and retrieve sensitive manufacturing data. Exemplo de código seguro
Secure Other
Registers used to store sensitive values read from fuses should be blocked during debug. These registers should be disconnected from the debug interface. What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de verificação de prevenção
How to prevent CWE-1243
- Architecture and Design / Implementation Disable access to security-sensitive information stored in fuses directly and also reflected from temporary storage locations when in debug mode.
Sinais de deteção
How to detect CWE-1243
Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.
Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.
Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.
O Plexicus deteta automaticamente o CWE-1243 e abre um PR de correção em menos de 60 segundos.
O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.
Perguntas frequentes O que é o CWE-1243?
Qual a gravidade do CWE-1243?
Que linguagens ou plataformas são afetadas pelo CWE-1243?
Como posso prevenir o CWE-1243?
Como é que o Plexicus deteta e corrige o CWE-1243?
Onde posso saber mais sobre o CWE-1243?
Frequently asked questions
O que é o CWE-1243?
This vulnerability occurs when security-critical data stored in hardware fuses is left unprotected and accessible during debug modes.
Qual a gravidade do CWE-1243?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-1243?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific.
Como posso prevenir o CWE-1243?
Disable access to security-sensitive information stored in fuses directly and also reflected from temporary storage locations when in debug mode.
Como é que o Plexicus deteta e corrige o CWE-1243?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1243 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-1243?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1243.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-1243
Recursos
Further reading
- MITRE — CWE-1243 oficial https://cwe.mitre.org/data/definitions/1243.html
- aes0_wrapper.sv https://github.com/HACK-EVENT/hackatdac21/blob/71103971e8204de6a61afc17d3653292517d32bf/piton/design/chip/tile/ariane/src/aes0/aes0_wrapper.sv#L56C1-L57C1
- fix cwe_1243 in aes0_wrapper.sv https://github.com/HACK-EVENT/hackatdac21/blob/cde1d9d6888bffab21d4b405ccef61b19c58dd3c/piton/design/chip/tile/ariane/src/aes0/aes0_wrapper.sv#L56
Pronto quando você estiver
Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.
O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.