Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-366 Base Rascunho
Race Condition within a Thread
This vulnerability occurs when two or more threads within the same application access and manipulate a shared resource (like a variable, data structure, or file) without proper synchronization.…
Definição
What is CWE-366?
This vulnerability occurs when two or more threads within the same application access and manipulate a shared resource (like a variable, data structure, or file) without proper synchronization. Because the threads can execute in an unpredictable order, they can corrupt the resource's state, leading to crashes, incorrect calculations, or data loss.
Unlike race conditions between separate processes, this issue happens entirely within a single program's threads. It's a flaw in the program's internal logic where the developer assumed certain operations would complete in a specific sequence, but the operating system's thread scheduler can interleave them arbitrarily. Common triggers include checking a flag or counter in one thread while another is modifying it, or performing non-atomic 'read-modify-write' operations on shared data.
To prevent this, developers must use proper synchronization primitives like mutexes, semaphores, or atomic operations. These tools create critical sections that ensure only one thread can access the shared resource at a time, guaranteeing predictable and valid states. Failing to implement synchronization correctly—or incorrectly assuming certain operations are thread-safe—leaves the application's behavior undefined and unreliable.
Impacto no mundo real
Real-world CVEs caused by CWE-366
-
Chain: two threads in a web browser use the same resource (CWE-366), but one of those threads can destroy the resource before the other has completed (CWE-416).
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable C
The following example demonstrates the weakness.
int foo = 0;
int storenum(int num) {
static int counter = 0;
counter++;
if (num > foo) foo = num;
return foo;
} Exemplo de código seguro
Secure 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-366
- Architecture and Design Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.
- Architecture and Design Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.
Sinais de deteção
How to detect CWE-366
O Plexicus deteta automaticamente o CWE-366 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-366?
Qual a gravidade do CWE-366?
Que linguagens ou plataformas são afetadas pelo CWE-366?
Como posso prevenir o CWE-366?
Como é que o Plexicus deteta e corrige o CWE-366?
Onde posso saber mais sobre o CWE-366?
Frequently asked questions
O que é o CWE-366?
This vulnerability occurs when two or more threads within the same application access and manipulate a shared resource (like a variable, data structure, or file) without proper synchronization. Because the threads can execute in an unpredictable order, they can corrupt the resource's state, leading to crashes, incorrect calculations, or data loss.
Qual a gravidade do CWE-366?
A MITRE classifica a probabilidade de exploração como Média — a exploração é realista mas normalmente requer condições específicas.
Que linguagens ou plataformas são afetadas pelo CWE-366?
MITRE lists the following affected platforms: C, C++, Java, C#.
Como posso prevenir o CWE-366?
Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment. Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads of execution.
Como é que o Plexicus deteta e corrige o CWE-366?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-366 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-366?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/366.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-366
CWE-362 Pai
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
A race condition occurs when multiple processes or threads access a shared resource simultaneously without proper coordination, creating a…
CWE-1223 Irmão
Race Condition for Write-Once Attributes
This vulnerability occurs when an untrusted software component wins a race condition and writes to a hardware register before the trusted…
CWE-1298 Irmão
Hardware Logic Contains Race Conditions
A hardware race condition occurs when security-critical logic circuits receive signals at slightly different times, creating temporary…
CWE-364 Irmão
Signal Handler Race Condition
A signal handler race condition occurs when a program's signal handling routine is vulnerable to timing issues, allowing its state to be…
CWE-367 Irmão
Time-of-check Time-of-use (TOCTOU) Race Condition
This vulnerability occurs when a program verifies a resource's state (like a file's permissions or existence) but then uses it after that…
CWE-368 Irmão
Context Switching Race Condition
This vulnerability occurs when an application switches between different security contexts (like privilege levels or domains) using a…
CWE-421 Irmão
Race Condition During Access to Alternate Channel
A race condition occurs when an application opens a secondary communication channel intended for an authorized user, but fails to secure…
CWE-689 Irmão
Permission Race Condition During Resource Copy
This vulnerability occurs when a system copies a file or resource but delays setting its final permissions until the entire copy operation…
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.