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-572 Variante Rascunho
Call to Thread run() instead of start()
This vulnerability occurs when a program incorrectly calls a thread's `run()` method directly, instead of using the `start()` method. This mistake causes the thread's code to execute within the…
Definição
What is CWE-572?
This vulnerability occurs when a program incorrectly calls a thread's `run()` method directly, instead of using the `start()` method. This mistake causes the thread's code to execute within the caller's current thread, bypassing the creation of a new, concurrent thread of execution.
Calling `run()` directly is almost always a programming error. The developer's intent is to launch new, concurrent operations using the `Thread` class. However, by calling `run()`, the code within that method simply executes as a normal function call in the existing thread. This defeats the entire purpose of using threads, leading to sequential execution and potential performance issues, as no true parallelism or concurrency is achieved.
The core issue is a misunderstanding of the Java threading model. The `start()` method is responsible for the native OS-level thread creation and scheduling, which then automatically calls the `run()` method in the new thread context. Bypassing `start()` means the `run()` method's code runs with the stack and context of the parent thread, which can cause unexpected behavior, block the UI, or break assumptions about thread-local data and synchronization.
Impacto no mundo real
Real-world CVEs caused by CWE-572
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
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 Java
The following excerpt from a Java program mistakenly calls run() instead of start().
Thread thr = new Thread() {
public void run() {
...
}
};
thr.run(); 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-572
- Implementation Use the start() method instead of the run() method.
Sinais de deteção
How to detect CWE-572
CWE-572
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-572?
Qual a gravidade do CWE-572?
Que linguagens ou plataformas são afetadas pelo CWE-572?
Como posso prevenir o CWE-572?
Como é que o Plexicus deteta e corrige o CWE-572?
Onde posso saber mais sobre o CWE-572?
Frequently asked questions
O que é o CWE-572?
This vulnerability occurs when a program incorrectly calls a thread's `run()` method directly, instead of using the `start()` method. This mistake causes the thread's code to execute within the caller's current thread, bypassing the creation of a new, concurrent thread of execution.
Qual a gravidade do CWE-572?
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-572?
MITRE lists the following affected platforms: Java.
Como posso prevenir o CWE-572?
Use the start() method instead of the run() method.
Como é que o Plexicus deteta e corrige o CWE-572?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-572 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-572?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/572.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-572
CWE-821 Pai
Incorrect Synchronization
This vulnerability occurs when multiple parts of a program, such as threads or processes, access a shared resource like a variable, file,…
CWE-1088 Irmão
Synchronous Access of Remote Resource without Timeout
This vulnerability occurs when an application makes a synchronous call to a remote service or resource but does not set a timeout, or sets…
CWE-1264 Irmão
Hardware Logic with Insecure De-Synchronization between Control and Data Channels
This vulnerability occurs when a hardware design incorrectly forwards data before its security or permission checks have finished…
CWE-574 Irmão
EJB Bad Practices: Use of Synchronization Primitives
This vulnerability occurs when an Enterprise JavaBeans (EJB) component improperly uses thread synchronization primitives, violating the…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.