CWE-1246 Base Incompleto

Improper Write Handling in Limited-write Non-Volatile Memories

This vulnerability occurs when a system fails to properly manage write operations on memory hardware that has a limited lifespan, such as Flash or EEPROM. Without correct wear leveling, specific…

Definição

What is CWE-1246?

This vulnerability occurs when a system fails to properly manage write operations on memory hardware that has a limited lifespan, such as Flash or EEPROM. Without correct wear leveling, specific memory cells wear out faster than intended, leading to premature device failure.
Many non-volatile memory chips, like NAND Flash and EEPROM, have a fundamental physical limitation: each memory cell can only be written to or erased a finite number of times. To maximize the overall lifespan of the storage device, a technique called wear leveling is essential. It works by dynamically mapping the system's logical write requests across different physical memory blocks, ensuring that write cycles are distributed evenly instead of repeatedly hitting the same cells. If wear leveling is missing or implemented incorrectly, it creates a critical weakness. An attacker can exploit this by deliberately targeting the same logical addresses with frequent write operations. This causes the underlying physical cells to wear out rapidly, potentially bricking the storage device or making data unreliable far sooner than its rated endurance, which constitutes a denial-of-service attack against the hardware itself.
Impacto no mundo real

Real-world CVEs caused by CWE-1246

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. 1

    An attacker can render a memory line unusable by repeatedly causing a write to the memory line.

  2. 2

    Below is example code from [REF-1058] that the user can execute repeatedly to cause line failure. W is the maximum associativity of any cache in the system; S is the size of the largest cache in the system.

  3. 3

    Without wear leveling, the above attack will be successful. Simple randomization of blocks will not suffice as instead of the original physical block, the randomized physical block will be worn out.

Exemplo de código vulnerável

Vulnerable C++

Below is example code from [REF-1058] that the user can execute repeatedly to cause line failure. W is the maximum associativity of any cache in the system; S is the size of the largest cache in the system.

Vulnerável C++ 
// Do aligned alloc of (W+1) arrays each of size S
 while(1) {

```
   for (ii = 0; ii < W + 1; ii++)
  	 array[ii].element[0]++;
 }
Payload do atacante

Below is example code from [REF-1058] that the user can execute repeatedly to cause line failure. W is the maximum associativity of any cache in the system; S is the size of the largest cache in the system.

Payload do atacante C++ 
// Do aligned alloc of (W+1) arrays each of size S
 while(1) {

```
   for (ii = 0; ii < W + 1; ii++)
  	 array[ii].element[0]++;
 }
Exemplo de código seguro

Secure Other

Without wear leveling, the above attack will be successful. Simple randomization of blocks will not suffice as instead of the original physical block, the randomized physical block will be worn out.

Seguro Other 
Wear leveling must be used to even out writes to the device.
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-1246

  • Architecture and Design / Implementation / Testing Include secure wear leveling algorithms and ensure they may not be bypassed.
Sinais de deteção

How to detect CWE-1246

SAST High

Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.

DAST Moderate

Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.

Runtime Moderate

Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.

Code review Moderate

Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-1246 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.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o CWE-1246?

This vulnerability occurs when a system fails to properly manage write operations on memory hardware that has a limited lifespan, such as Flash or EEPROM. Without correct wear leveling, specific memory cells wear out faster than intended, leading to premature device failure.

Qual a gravidade do CWE-1246?

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-1246?

MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, System on Chip, Memory Hardware, Storage Hardware.

Como posso prevenir o CWE-1246?

Include secure wear leveling algorithms and ensure they may not be bypassed.

Como é que o Plexicus deteta e corrige o CWE-1246?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1246 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-1246?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1246.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-1246

CWE-400 Pai

Uncontrolled Resource Consumption

This vulnerability occurs when an application fails to properly manage a finite resource, allowing an attacker to exhaust it and cause a…

CWE-1235 Irmão

Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations

This weakness occurs when a program relies on automatic boxing and unboxing of primitive types within performance-sensitive code sections,…

CWE-405 Irmão

Asymmetric Resource Consumption (Amplification)

This vulnerability occurs when a system allows an attacker to trigger a disproportionate amount of resource consumption—like CPU, memory,…

CWE-770 Irmão

Allocation of Resources Without Limits or Throttling

This vulnerability occurs when a system allows users or processes to request resources without any built-in caps or rate limits. Think of…

CWE-771 Irmão

Missing Reference to Active Allocated Resource

This vulnerability occurs when software loses track of a resource it has allocated, like memory or a file handle, preventing the system…

CWE-779 Irmão

Logging of Excessive Data

This vulnerability occurs when an application records more information than necessary in its logs, making log files difficult to analyze…

CWE-920 Irmão

Improper Restriction of Power Consumption

This vulnerability occurs when software running on a power-constrained device, like a battery-powered mobile or embedded system, fails to…

Recursos

Further reading

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.

Começar grátis Reservar uma demo