CWE-666 Classe Rascunho

Operation on Resource in Wrong Phase of Lifetime

This vulnerability occurs when software interacts with a resource—like memory, a file, or a network connection—at an incorrect stage of its existence, leading to crashes, data corruption, or…

Definição

What is CWE-666?

This vulnerability occurs when software interacts with a resource—like memory, a file, or a network connection—at an incorrect stage of its existence, leading to crashes, data corruption, or unpredictable behavior.
Every resource in a program has a distinct lifecycle: it's created (initialized), used for its intended purpose, and finally cleaned up (released). Each of these phases has specific rules. A common mistake is trying to use a resource before it's fully ready—like reading from an uninitialized memory buffer—or after it's been disposed of, such as closing an already-closed file handle. These operations violate the expected sequence and directly cause instability. To prevent this, developers must explicitly manage state. Ensure initialization is complete before use, validate the resource is in an 'active' state for operations, and avoid repeated or premature release. Using design patterns like RAII (Resource Acquisition Is Initialization) or implementing clear state flags can enforce the correct order and make invalid phase transitions obvious bugs during development.
Impacto no mundo real

Real-world CVEs caused by CWE-666

  • CVE-2006-5051

    Chain: Signal handler contains too much functionality (CWE-828), introducing a race condition (CWE-362) that leads to a double free (CWE-415).

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    The following code shows a simple example of a double free vulnerability.

  2. 2

    Double free vulnerabilities have two common (and sometimes overlapping) causes:

  3. 3

    - Error conditions and other exceptional circumstances - Confusion over which part of the program is responsible for freeing the memory

  4. 4

    Although some double free vulnerabilities are not much more complicated than this example, most are spread out across hundreds of lines of code or even different files. Programmers seem particularly susceptible to freeing global variables more than once.

Exemplo de código vulnerável

Vulnerable C

The following code shows a simple example of a double free vulnerability.

Vulnerável C 
char* ptr = (char*)malloc (SIZE);
   ...
   if (abrt) { 
  	 free(ptr); 
   }
   ...
   free(ptr);
Exemplo de código seguro

Secure pseudo

Seguro pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
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-666

  • Architecture and Design Follow the resource's lifecycle from creation to release.
Sinais de deteção

How to detect CWE-666

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

This vulnerability occurs when software interacts with a resource—like memory, a file, or a network connection—at an incorrect stage of its existence, leading to crashes, data corruption, or unpredictable behavior.

Qual a gravidade do CWE-666?

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

A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.

Como posso prevenir o CWE-666?

Follow the resource's lifecycle from creation to release.

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-666

CWE-664 Pai

Improper Control of a Resource Through its Lifetime

This vulnerability occurs when software fails to properly manage a resource throughout its entire lifecycle—from creation and active use…

CWE-118 Irmão

Incorrect Access of Indexable Resource ('Range Error')

This vulnerability occurs when software fails to properly check the boundaries of an indexed resource, like an array, buffer, or file,…

CWE-1229 Irmão

Creation of Emergent Resource

This vulnerability occurs when a system's normal operations unintentionally create new, exploitable resources that attackers can use to…

CWE-1250 Irmão

Improper Preservation of Consistency Between Independent Representations of Shared State

This vulnerability occurs when a system with multiple independent components (like distributed services or separate hardware units) each…

CWE-1329 Irmão

Reliance on Component That is Not Updateable

This vulnerability occurs when a product depends on a component that cannot be updated or patched to fix security flaws or critical bugs.

CWE-221 Irmão

Information Loss or Omission

This weakness occurs when an application fails to log critical security events or records them inaccurately, which can misguide security…

CWE-372 Irmão

Incomplete Internal State Distinction

This vulnerability occurs when an application fails to accurately track its own operational state. The system incorrectly assumes it's in…

CWE-400 Irmão

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-404 Irmão

Improper Resource Shutdown or Release

This vulnerability occurs when a program fails to properly close or release a system resource—like a file handle, database connection, or…

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