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-585 Variante Rascunho
Empty Synchronized Block
An empty synchronized block is a Java code construct where a synchronized block exists but contains no executable statements inside it.
Definição
What is CWE-585?
An empty synchronized block is a Java code construct where a synchronized block exists but contains no executable statements inside it.
An empty synchronized block is a logic flaw that fails to provide any actual thread safety or mutual exclusion. While the synchronized keyword is present, the block does nothing to protect shared data or coordinate threads, leaving critical sections of your code vulnerable to race conditions and concurrency bugs.
This issue often arises during code maintenance, such as when a developer comments out or removes the internal logic for debugging but forgets to remove the now-useless synchronization wrapper. It serves as a clear red flag for developers to review that section of code, as it either indicates missing functionality or unnecessary overhead that can harm performance without benefit.
Impacto no mundo real
Real-world CVEs caused by CWE-585
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 code attempts to synchronize on an object, but does not execute anything in the synchronized block. This does not actually accomplish anything and may be a sign that a programmer is wrestling with synchronization but has not yet achieved the result they intend.
synchronized(this) { } Exemplo de código seguro
Secure Java
Instead, in a correct usage, the synchronized statement should contain procedures that access or modify data that is exposed to multiple threads. For example, consider a scenario in which several threads are accessing student records at the same time. The method which sets the student ID to a new value will need to make sure that nobody else is accessing this data at the same time and will require synchronization.
public void setID(int ID){
synchronized(this){
this.ID = ID;
}
} 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-585
- Implementation When you come across an empty synchronized statement, or a synchronized statement in which the code has been commented out, try to determine what the original intentions were and whether or not the synchronized block is still necessary.
Sinais de deteção
How to detect CWE-585
CWE-585
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-585?
Qual a gravidade do CWE-585?
Que linguagens ou plataformas são afetadas pelo CWE-585?
Como posso prevenir o CWE-585?
Como é que o Plexicus deteta e corrige o CWE-585?
Onde posso saber mais sobre o CWE-585?
Frequently asked questions
O que é o CWE-585?
An empty synchronized block is a Java code construct where a synchronized block exists but contains no executable statements inside it.
Qual a gravidade do CWE-585?
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-585?
MITRE lists the following affected platforms: Java.
Como posso prevenir o CWE-585?
When you come across an empty synchronized statement, or a synchronized statement in which the code has been commented out, try to determine what the original intentions were and whether or not the synchronized block is still necessary.
Como é que o Plexicus deteta e corrige o CWE-585?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-585 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-585?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/585.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-585
CWE-1071 Pai
Empty Code Block
An empty code block occurs when a section of source code, such as a conditional statement or function body, contains no executable…
CWE-1069 Irmão
Empty Exception Block
This weakness occurs when a try-catch or try-finally block is present but contains no code to handle the caught exception or perform…
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ê.