CWE-484: Omitted Break Statement in Switch | Codefreex Skip to content

Security weakness

CWE-484 Omitted Break Statement in Switch

A base-level weakness that can lead to effects that depend on context. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-484?

Omitted Break Statement in Switch: 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.

Business impact

What CWE-484 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Other

Effects that depend on context

The impact depends on where the weakness sits in your code and what it can reach.

  • Alter Execution Logic

Free security check

Is CWE-484 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-484

Omitted Break Statement in Switch

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.

Weakness ID
CWE-484
Type
Base
Status
Draft
Likelihood of exploit
Medium
Applies to
C, C++, Java, C#, PHP
Introduced during
Implementation

Prevention

How to fix CWE-484, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    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.
    • The functionality of omitting a break statement could be clarified with an if statement. This method is much safer.

Detection and evidence

How CWE-484 is found, and where it has hit

The testing methods MITRE recommends for finding it.

How it is detected

  • White BoxOmission of a break statement might be intentional, in order to support fallthrough. Automated detection methods might therefore be erroneous. Semantic understanding of expected product behavior is required to interpret whether the code is correct.
  • Black BoxSince this weakness is associated with a code construct, it would be indistinguishable from other errors that produce the same behavior.
  • Automated Static AnalysisAutomated 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.

How we fix it

From finding to fixed: how Codefreex closes CWE-484

  1. Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-484: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-484?

CWE-484, “Omitted Break Statement in Switch”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. 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.

How serious is CWE-484?

MITRE rates the likelihood of exploit as Medium. It can affect other, with impacts such as alter execution logic. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-484?

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. The functionality of omitting a break statement could be clarified with an if statement. This method is much safer.

Can Codefreex check my site for CWE-484?

Yes. A senior engineer reviews your site, store or app for CWE-484 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Which technologies does CWE-484 affect?

MITRE lists it as applicable to C, C++, Java, C#, PHP. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.

Free security check

Find out if CWE-484 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.