CWE-1071
Weakness AllowedEmpty Code Block
Abstraction: Base · Status: Incomplete
The source code contains a block that does not contain any code, i.e., the block is empty.
Mapping guidance
This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
Modes of introduction
For some programming languages and constructs, an empty block might be allowed by the syntax. While an empty code block might be intentional, it could accidentally occur when the developer did not finish implementation, accidental code deletion, unexpected macro expansion, etc.
Detection methods
Automated Static Analysis
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.)
Effectiveness: High
Content history
updated Relationships, Type
updated Relationships
updated Mapping_Notes
updated Demonstrative_Examples
updated Demonstrative_Examples
updated Applicable_Platforms, Detection_Factors, Time_of_Introduction
updated Background_Details, Common_Consequences, Description, Modes_of_Introduction
0 vulnerabilities reference this CWE, most recent first.
No vulnerabilities reference this CWE.
No mitigation information available for this CWE.
No CAPEC attack patterns related to this CWE.