BaseDraft

CWE-484Omitted Break Statement in Switch

Category: other

Description

The product omits a break statement within a switch or similar construct, causing code associated with multiple conditions to execute. This can cause problems when the programmer only intended to execute code associated with one condition. This can lead to critical code executing in situations where it should not.

Common consequences· 1

  • Other — Alter Execution Logic
    This weakness can cause unintended logic to be executed and other unexpected application behavior.

Potential mitigations· 2

  • [Implementation]Omitting a break statement so that one may fall through is often indistinguishable from an error, and therefore should be avoided. If you need to use fall-through capabilities, make sure that you have clearly documented this within the switch statement, and ensure that you have examined all the logical possibilities.
  • [Implementation]The functionality of omitting a break statement could be clarified with an if statement. This method is much safer.

References

  1. https://cwe.mitre.org/data/definitions/484.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Unchecked Input for Loop Condition
CWE
Incorrect Control Flow Scoping
CWE
Incorrect Short Circuit Evaluation
CWE
Improper Adherence to Coding Standards
CWE
Improper Cleanup on Thrown Exception
CWE
Uncontrolled Recursion
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.