Comparing a function pointer to a value that is not a null function pointer of the same type will be diagnosed because it typically indicates programmer error and can result in unexpected behavior. Implicit comparisons will be diagnosed, as well.

Noncompliant Code Example

In this noncompliant code example, the addresses of the POSIX functions getuid and geteuid are compared for equality to 0. Because no function address shall be null, the first subexpression will always evaluate to false (0), and the second subexpression always to true (nonzero). Consequently, the entire expression will always evaluate to true, leading to a potential security vulnerability.

/* First the options that are allowed only for root */
if (getuid == 0 || geteuid != 0) {
  /* ... */
}

Noncompliant Code Example

In this noncompliant code example, the function pointers getuid and geteuid are compared to 0. This example is from an actual vulnerability (VU#837857) discovered in some versions of the X Window System server. The vulnerability exists because the programmer neglected to provide the open and close parentheses following the geteuid() function identifier. As a result, the geteuid token returns the address of the function, which is never equal to 0. Consequently, the or condition of this if statement is always true, and access is provided to the protected block for all users. Many compilers issue a warning noting such pointless expressions. Therefore, this coding error is normally detected by adherence to MSC00-C. Compile cleanly at high warning levels.

/* First the options that are allowed only for root */
if (getuid() == 0 || geteuid != 0) {
  /* ... */
}

Compliant Solution

The solution is to provide the open and close parentheses following the geteuid token so that the function is properly invoked:

/* First the options that are allowed only for root */
if (getuid() == 0 || geteuid() != 0) {
  /* ... */
}

Compliant Solution

A function pointer can be compared to a null function pointer of the same type:

/* First the options that are allowed only for root */ 
if (getuid == (uid_t(*)(void))0 || geteuid != (uid_t(*)(void))0) { 
  /* ... */ 
} 

This code should not be diagnosed by an analyzer.

Noncompliant Code Example

In this noncompliant code example, the function pointer do_xyz is implicitly compared unequal to 0:

int do_xyz(void); 
 
int f(void) {
/* ... */
  if (do_xyz) { 
    return -1; /* Indicate failure */ 
  }
/* ... */
  return 0;
} 

Compliant Solution

In this compliant solution, the function do_xyz() is invoked and the return value is compared to 0:

int do_xyz(void); 
 
int f(void) {
/* ... */ 
  if (do_xyz()) { 
    return -1; /* Indicate failure */
  }
/* ... */
  return 0;  
} 

Risk Assessment

Errors of omission can result in unintended program flow.

Automated Detection

Tool	Version	Checker	Description
Astrée		function-name-constant-comparison	Partially checked
Coverity		BAD_COMPARE	Can detect the specific instance where the address of a function is compared against 0, such as in the case of geteuid versus getuid() in the implementation-specific details
GCC			Can detect violations of this recommendation when the -Wall flag is used
Helix QAC		C0428, C3004, C3344
Klocwork		CWARN.NULLCHECK.FUNCNAME CWARN.FUNCADDR
LDRA tool suite		99 S	Partially implemented
Parasoft C/C++test		CERT_C-EXP16-a	Function address should not be compared to zero
PC-lint Plus		2440, 2441	Partially supported: reports address of function, array, or variable directly or indirectly compared to null
PVS-Studio		V516, V1058
RuleChecker		function-name-constant-comparison	Partially checked

Related Vulnerabilities

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

Related Guidelines

Bibliography