GitHub
CERT Secure Coding

DCL41-C. Do not declare variables inside a switch statement before the first case label

According to the C Standard, 6.8.5.3, paragraph 4 [ ISO/IEC 9899:2024 ],

A switch statement causes control to jump to, into, or past the statement that is the switch body , depending on the value of a controlling expression, and on the presence of a default label and the values of any case labels on or in the switch body. A case or default label is accessible only within the closest enclosing switch statement.

If a programmer declares variables, initializes them before the first case statement, and then tries to use them inside any of the case statements, those variables will have scope inside the switch block but will not be initialized and will consequently contain indeterminate values.  Reading such values also violates EXP33-C. Do not read uninitialized memory .

Noncompliant Code Example

This noncompliant code example declares variables and contains executable statements before the first case label within the switch statement:

Non-compliant code
#include <stdio.h>
 
extern void f(int i);
 
void func(int expr) {
  switch (expr) {
    int i = 4;
    f(i);
  case 0:
    i = 17;
    /* Falls through into default code */
  default:
    printf("%d\n", i);
  }
}

Implementation Details

When the preceding example is executed on GCC 4.8.1, the variable i is instantiated with automatic storage duration within the block, but it is not initialized. Consequently, if the controlling expression expr has a nonzero value, the call to printf() will access an indeterminate value of i . Similarly, the call to f() is not executed.

Value of exprOutput
017
NonzeroIndeterminate

Compliant Solution

In this compliant solution, the statements before the first case label occur before the switch statement:

Compliant code
#include <stdio.h>
 
extern void f(int i);
 
int func(int expr) {
  /*
   * Move the code outside the switch block; now the statements
   * will get executed.
   */
  int i = 4;
  f(i);

  switch (expr) {
    case 0:
      i = 17;
      /* Falls through into default code */
    default:
      printf("%d\n", i);
  }
  return 0;
}

Risk Assessment

Using test conditions or initializing variables before the first case statement in a switch block can result in unexpected behavior and undefined behavior 20 .

Rule Severity Likelihood Detectable Repairable Priority Level
DCL41-C Medium Unlikely Yes Yes P6 L2

Automated Detection

Tool

Version

Checker

Description

Astrée25.10

switch-skipped-code

Fully checked
Axivion Bauhaus Suite7.2.0CertC-DCL41Fully implemented
Clang3.9 -Wsometimes-uninitialized

CodeSonar9.1p0LANG.STRUCT.SW.BADMalformed switch Statement
Coverity2017.07

MISRA C 2004 Rule 15.0

MISRA C 2012 Rule 16.1

Implemented
Cppcheck Premium
24.11.0

premium-cert-dcl41-c


Helix QAC2025.2C2008, C2882, C3234Fully implemented
Klocwork2025.2CERT.DCL.SWITCH.VAR_BEFORE_CASEFully implemented
LDRA tool suite9.7.1385 SFully implemented
Parasoft C/C++test
2025.2
CERT_C-DCL41-a

A switch statement shall only contain switch labels and switch clauses, and no other code

PC-lint Plus

1.4

527

Assistance provided

Polyspace Bug Finder

R2025b

CERT C: Rule DCL41-C

Checks for ill-formed switch statements (rule partially covered)

PVS-Studio

7.42

V622
RuleChecker

25.10

switch-skipped-code

Fully checked
TrustInSoft Analyzer

1.38

initialisationExhaustively detects undefined behavior (see the compliant and the non-compliant example ).

Search for vulnerabilities resulting from the violation of this rule on the CERT website .

Key here (explains table format and definitions)

TaxonomyTaxonomy itemRelationship
MISRA C:2012Rule 16.1 (required)Prior to 2018-01-12: CERT: Unspecified Relationship

Bibliography

[ ISO/IEC 9899:2024 ]6.8.5.3, "The switch Statement"