Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-1270 Base Incompleto
Generation of Incorrect Security Tokens
This vulnerability occurs when a system's security token mechanism, designed to control permissions for different entities or agents, generates tokens that are fundamentally flawed or incorrect.
Definição
What is CWE-1270?
This vulnerability occurs when a system's security token mechanism, designed to control permissions for different entities or agents, generates tokens that are fundamentally flawed or incorrect.
In Systems-on-a-Chip (SoC) and similar hardware, security tokens act as digital IDs that define what actions (like read, write, or reset) each hardware agent is allowed to perform. These tokens are assigned based on an agent's trust level. If the token generation logic is broken, it can assign duplicate tokens to multiple agents or assign multiple conflicting tokens to a single agent.
This flawed assignment breaks the fundamental security model. It can lead to severe consequences, including system crashes (Denial-of-Service), privilege escalation where a low-trust agent gains high-level access, or unauthorized actions that compromise the entire chip's security and data integrity.
Impacto no mundo real
Real-world CVEs caused by CWE-1270
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
Consider a system with a register for storing an AES key for encryption or decryption. The key is 128 bits long implemented as a set of four 32-bit registers. The key registers are assets, and register, AES_KEY_ACCESS_POLICY, is defined to provide necessary access controls. The access-policy register defines which agents, using a Security Token, may access the AES-key registers. Each bit in this 32-bit register is used to define a Security Token. There could be a maximum of 32 Security Tokens that are allowed access to the AES-key registers. When set (bit = "1") bit number allows action from an agent whose identity matches that bit number. If Clear (bit = "0") the action is disallowed for the corresponding agent.
- 2
Assume the system has two agents: a Main-controller and an Aux-controller. The respective Security Tokens are "1" and "2". | Register | Description | Default | | --- | --- | --- | | AES_ENC_DEC_KEY_0 | AES key [0:31] for encryption or decryption | 0x00000000 | | AES_ENC_DEC_KEY_1 | AES key [32:63] for encryption or decryption | 0x00000000 | | AES_ENC_DEC_KEY_2 | AES key [64:95] for encryption or decryption | 0x00000000 | | AES_ENC_DEC_KEY_3 | AES key [96:127] for encryption or decryption | 0x00000000 | | AES_KEY_ACCESS_POLICY | AES key access register [31:0] | 0x00000002 |
- 3
An agent with a Security Token "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_3 registers. As per the above access policy, the AES-Key-access policy allows access to the AES-key registers if the security Token is "1".
- 4
Both agents have access to the AES-key registers.
Exemplo de código vulnerável
Vulnerable Other
An agent with a Security Token "1" has access to AES_ENC_DEC_KEY_0 through AES_ENC_DEC_KEY_3 registers. As per the above access policy, the AES-Key-access policy allows access to the AES-key registers if the security Token is "1".
The SoC incorrectly generates Security Token "1" for every agent. In other words, both Main-controller and Aux-controller are assigned Security Token "1". Exemplo de código seguro
Secure Other
Both agents have access to the AES-key registers.
The SoC should correctly generate Security Tokens, assigning "1" to the Main-controller and "2" to the Aux-controller 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-1270
- Architecture and Design / Implementation - Generation of Security Tokens should be reviewed for design inconsistency and common weaknesses. - Security-Token definition and programming flow should be tested in pre-silicon and post-silicon testing.
Sinais de deteção
How to detect CWE-1270
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-1270 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-1270?
Qual a gravidade do CWE-1270?
Que linguagens ou plataformas são afetadas pelo CWE-1270?
Como posso prevenir o CWE-1270?
Como é que o Plexicus deteta e corrige o CWE-1270?
Onde posso saber mais sobre o CWE-1270?
Frequently asked questions
O que é o CWE-1270?
This vulnerability occurs when a system's security token mechanism, designed to control permissions for different entities or agents, generates tokens that are fundamentally flawed or incorrect.
Qual a gravidade do CWE-1270?
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-1270?
MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific.
Como posso prevenir o CWE-1270?
- Generation of Security Tokens should be reviewed for design inconsistency and common weaknesses. - Security-Token definition and programming flow should be tested in pre-silicon and post-silicon testing.
Como é que o Plexicus deteta e corrige o CWE-1270?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1270 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-1270?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1270.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-1270
CWE-284 Pai
Improper Access Control
The software fails to properly limit who can access a resource, allowing unauthorized users or systems to interact with it.
CWE-1191 Irmão
On-Chip Debug and Test Interface With Improper Access Control
This vulnerability occurs when a hardware chip's debug or test interface (like JTAG) lacks proper access controls. Without correct…
CWE-1220 Irmão
Insufficient Granularity of Access Control
This vulnerability occurs when a system's access controls are too broad, allowing unauthorized users or processes to read or modify…
CWE-1224 Irmão
Improper Restriction of Write-Once Bit Fields
This vulnerability occurs when hardware write-once protection mechanisms, often called 'sticky bits,' are incorrectly implemented,…
CWE-1231 Irmão
Improper Prevention of Lock Bit Modification
This vulnerability occurs when hardware or firmware uses a lock bit to protect critical system registers or memory regions, but fails to…
CWE-1233 Irmão
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
This vulnerability occurs when a hardware device uses a lock bit to protect critical configuration registers, but the lock fails to…
CWE-1252 Irmão
CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations
This vulnerability occurs when a CPU's hardware is not set up to enforce a strict separation between writing data to memory and executing…
CWE-1257 Irmão
Improper Access Control Applied to Mirrored or Aliased Memory Regions
This vulnerability occurs when a hardware design maps the same physical memory to multiple addresses (aliasing or mirroring) but fails to…
CWE-1259 Irmão
Improper Restriction of Security Token Assignment
This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly secure its Security Token mechanism. These tokens control which…
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.