CWE-1071 Base Incompleto

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

Definição

What is CWE-1071?

An empty code block occurs when a section of source code, such as a conditional statement or function body, contains no executable statements.
Empty blocks can appear in various places like if/else conditionals, loops, function definitions, or exception handlers. While sometimes intentionally used as a placeholder, they often signal problems like incomplete features, accidentally deleted logic, or unexpected behavior from macros or code generators. For developers, these empty blocks are a red flag. Even if the language syntax allows them, they frequently violate API contracts or expected program behavior, leading to silent failures or security issues where an action is assumed but never executed. Code reviews should actively identify and justify any empty block to prevent unintentional gaps in application logic.
Impacto no mundo real

Real-world CVEs caused by CWE-1071

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

    In the following Java example, the code catches an ArithmeticException.

  2. 2

    Since the exception block is empty, no action is taken.

  3. 3

    In the code below the exception has been logged and the bad execution has been handled in the desired way allowing the program to continue in an expected way.

  4. 4

    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.

  5. 5

    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.

Exemplo de código vulnerável

Vulnerable Java

In the following Java example, the code catches an ArithmeticException.

Vulnerável Java 
public class Main {
  	public static void main(String[] args) { 
  		int a = 1; 
  		int b = 0; 
  		int c = 0;
  		try { 
  			c = a / b;
  		} catch(ArithmeticException ae) { 
  		}
  	}
  }
Exemplo de código seguro

Secure Java

In the code below the exception has been logged and the bad execution has been handled in the desired way allowing the program to continue in an expected way.

Seguro Java 
public class Main {
  	public static void main(String[] args) { 
  		int a = 1; 
  		int b = 0; 
  		int c = 0;
  		try { 
  			c = a / b;
  		} catch(ArithmeticException ae) { 
  			log.error("Divided by zero detected, setting to -1."); 
  			c = -1;
  		}
  	}
  }
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-1071

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Sinais de deteção

How to detect CWE-1071

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

An empty code block occurs when a section of source code, such as a conditional statement or function body, contains no executable statements.

Qual a gravidade do CWE-1071?

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

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

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

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

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

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

Fraquezas relacionadas

Weaknesses related to CWE-1071

CWE-1164 Pai

Irrelevant Code

Irrelevant code refers to sections of a program that have no impact on its execution, data, or logic. Removing this code would not change…

CWE-107 Irmão

Struts: Unused Validation Form

This vulnerability occurs when a Struts application contains validation form definitions that are no longer linked to any active form or…

CWE-110 Irmão

Struts: Validator Without Form Field

This vulnerability occurs when a Struts application's validation configuration file references form fields that no longer exist in the…

CWE-561 Irmão

Dead Code

Dead code refers to sections of a program that can never run during normal execution, effectively making them inactive and unreachable.

CWE-563 Irmão

Assignment to Variable without Use

This vulnerability occurs when a value is stored in a variable, but that variable is never read or used in subsequent code, creating a…

CWE-1069 Filho

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…

CWE-585 Filho

Empty Synchronized Block

An empty synchronized block is a Java code construct where a synchronized block exists but contains no executable statements inside it.

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