Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Opening and closing braces for if, for, or while statements should always be used , even if the statement's body contains only a single statement. Braces improve the uniformity and readability of code.

More importantlyimportant, when inserting an additional statement into a body containing only a single statement, it is easy to forget to add braces because the indentation gives strong (but misleading) guidance to the structure.

Noncompliant Code Example

This noncompliant code example uses an if statement without braces to authenticate the user.

...

Code Block
bgColor#ffcccc
int login;

if (invalid_login())
  login = 0;
else
  System.out.println("Login is valid\n");  // debugging line added here
  login = 1;                               // this line always gets executed, regardless of a valid login!

The code indentation disguises the functionality of the program, potentially leading to a security breach.

Compliant Solution

In this compliant solution, opening and closing braces are used even when the body is a single statement.

Code Block
bgColor#CCCCFF
int login;

if (invalid_login()) {
  login = 0;
} else {
  login = 1;
}

Noncompliant Code Example

This noncompliant code example nests an if statement within another if statement without braces around the if and else bodies.

Code Block
bgColor#ffcccc
int privileges;

if (invalid_login())
  if (allow_guests())
    privileges = GUEST;
else
  privileges = ADMINISTRATOR;

...

This is a vulnerability because unauthorized users can obtain administrator privileges.

Compliant Solution

In this compliant solution, adding braces removes the ambiguity and ensures that privileges are correctly assigned.

...

CERT C Secure Coding Standard: "EXP19-C. Use braces for the body of an if, for, or while statement"

Bibliography

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fbf706f60e20f46b-4df55321-426346f8-bee1b01f-169de6479697656b11f7146a"><ac:plain-text-body><![CDATA[

[[GNU 2010

AA. References#GNU 10]]

[Coding Standards, Section 5.3, "Clean Use of C Constructs"

http://www.gnu.org/prep/standards/standards.html#Syntactic-Conventions]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d3b6a2b5ed830ce3-e1166009-48ab497e-b0b38c7b-820cde85184f12aec73d8a03"><ac:plain-text-body><![CDATA[

[[Rogue 2000

AA. References#Rogue 2000]]

Rule 76: Use block statements instead of expression statements in control flow constructs

]]></ac:plain-text-body></ac:structured-macro>

...