Page History

if (foo(x = y)) { /* ... */ } 

Noncompliant Code Example

This noncompliant code example has a typo that results in an assignment rather than a comparison.

while (ch == ' \t' && ch == '\t ' && ch == '\n') {
  /* ... */
}

Many compilers will warn about this condition. This coding error would typically be eliminated by adherence to MSC00-C. Compile cleanly at high warning levels. Although this code compiles, it will cause unexpected behavior to an unsuspecting programmer. If the intent was to verify a string such as a password, user name, or group user ID, the code may produce significant vulnerabilities and require significant debugging.

Compliant Solution (RHS Variable)

When comparisons are made against things other than variables, placing the variable on the right of the comparison operation can prevent a spurious assignment.

In this code example, the constants are placed on the left-hand side of each comparison, ensuring a compiler diagnostic at any warning level. If the programmer were to inadvertently use an assignment operator, the statement would try to assign a ch to a '\t' and become invalid.

while (' \t' == ch && '\t ' == ch && '\n' == ch) {
  /* ... */
}

Thanks to the compiler, the typo will be easily spotted and fixed.

while (' \t' == ch && '\t ' == ch && '\n' == ch) {
  /* ... */
}

As a result, any mistaken use of the assignment operator that could otherwise create a vulnerability for operations such as string verification will result in a compiler diagnostic regardless of compiler, warning level, or implementation.

Risk Assessment