You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 62 Next »

Bitwise operators include the complement operator ~, bitwise shift operators >> and <<, bitwise AND operator &, bitwise exclusive OR operator ^, and bitwise inclusive OR operator |. Bitwise operators should only be used with unsigned integer operands, as the results of some bitwise operations on signed integers is implementation defined.

Noncompliant Code Example (Right Shift)

The right-shift operation may be implemented as either an arithmetic (signed) shift or a logical (unsigned) shift. If E1 in the expression E1 >> E2 has a signed type and a negative value, the resulting value is implementation defined. Also, a bitwise shift can result in undefined behavior. (See rule INT34-C. Do not shift a negative number of bits or more bits than exist in the operand.)

This noncompliant code example can result in an error condition on implementations in which an arithmetic shift is performed, and the sign bit is propagated as the number is shifted [Dowd 2006].

int rc = 0;
int stringify = 0x80000000;
char buf[sizeof("256")];
rc = snprintf(buf, sizeof(buf), "%u", stringify >> 24);
if (rc == -1 || rc >= sizeof(buf)) {
  /* handle error */
}

In this example, stringify >> 24 evaluates to 0xFFFFFF80, or 4,294,967,168. When converted to a string, the resulting value "4294967168" is too large to store in buf and is truncated by snprintf().

If this code had been implemented using sprintf() instead of snprintf(), this noncompliant code example would have resulted in a buffer overflow.

Compliant Solution (right shift)

In this compliant solution, stringify is declared as an unsigned integer. The value of the result of the right shift operation is the integral part of the quotient of stringify / 2^24.

int rc = 0;
unsigned int stringify = 0x80000000;
char buf[sizeof("256")];
rc = snprintf(buf, sizeof(buf), "%u", stringify >> 24);
if (rc == -1 || rc >= sizeof(buf)) {
  /* handle error */
}

Also, consider using the sprintf_s() function defined in ISO/IEC TR 24731-1, instead of snprintf(), to provide some additional checks. (See recommendation STR07-C. Use the bounds-checking interfaces for remediation of existing string manipulation code.)

Exceptions

INT13-EX1: When used as bit flags, it is acceptable to use preprocessor macros as arguments to the & and | operators even if the value is not explicitly declared as unsigned.

fd = open(file_name, UO_WRONLY | UO_CREAT | UO_EXCL | UO_TRUNC, 0600);

INT13-EX2: If the right hand side operand to a shift operator is known at compile time, it is acceptable for the value to be represented with a signed type provided it is positive.

#define SHIFT 24
foo = 15u >> SHIFT;

Risk Assessment

Performing bitwise operations on signed numbers can lead to buffer overflows and the execution of arbitrary code by an attacker in some cases, unexpected or implementation defined behavior in others.

Recommendation

Severity

Likelihood

Remediation Cost

Priority

Level

INT13-C

high

unlikely

medium

P6

L2

Automated Detection

Tool

Version

Checker

Description

9.7.1

 

 

Fortify SCA

V. 5.0

 

with the CERT C Rule Pack can detect violations of this recommendation

Splint

3.1.1

 

 

Compass/ROSE

 

 

can detect violations of this rule. In particular, it flags bitwise operations that involved variables not declared with unsigned type

Related Vulnerabilities

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

Related Guidelines

CERT C++ Secure Coding Standard: INT13-CPP. Use bitwise operators only on unsigned operands

ISO/IEC 2003 Section 6.5.7, "Bitwise shift operators"

ISO/IEC 9899:1999 Section 6.5.7, "Bitwise shift operators"

ISO/IEC TR 24772 "STR Bit Representations," "XYY Wrap-around Error," and "XZI Sign Extension Error"

MITRE CWE: CWE-682, "Incorrect Calculation"

Bibliography

[Dowd 2006] Chapter 6, "C Language Issues"


      04. Integers (INT)      

  • No labels