Comparing a function pointer to a value that is not a null function pointer of the same type will be diagnosed because this it typically indicates programmer error and can result in unexpected behavior. Implicit comparisons will be diagnosed, as well.
...
In this noncompliant code example, the addresses of the POSIX ® functions getuid
and geteuid
are compared for equality to 0. Since the address of Because no function is address shall be null, the first subexpression will always evaluate to false (zero0) while , and the second subexpression always to true (non-zerononzero). ThusConsequently, the entire expression will always evaluate to true, leading to a potential security vulnerability.
Code Block | ||||
---|---|---|---|---|
| ||||
/* First the options that are allowed only allowed for root */ if (getuid == 0 || geteuid != 0) { /* ... */ } |
...
In this noncompliant code example, the function pointers getuid
and geteuid
are compared to 0. This noncompliant code 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 zero0. As a resultConsequently, 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.
Code Block | ||||
---|---|---|---|---|
| ||||
/* First the options that are allowed only allowed for root */ if (getuid() == 0 || geteuid != 0) { /* ... */ } |
...
The solution is to provide the open and close parentheses following the geteuid
token so that the function is properly invoked.:
Code Block | ||||
---|---|---|---|---|
| ||||
/* First the options that are allowed only allowed for root */ if (getuid() == 0 || geteuid() != 0) { /* ... */ } |
...
A function pointer can be compared to a null function pointer of the same type.:
Code Block | ||||
---|---|---|---|---|
| ||||
/* First the options that are allowed only allowed for root */ if (getuid == (uid_t(*)(void))0 || geteuid != (uid_t(*)(void))0) { /* ... */ } |
...
In this noncompliant code example, the function pointer do_xyz
is implicitly compared unequal to 0.:
Code Block | ||||
---|---|---|---|---|
| ||||
int do_xyz(void); int f(void) { /* ... */ if (do_xyz) { return -1; /* handle errorIndicate failure */ } /* ... */ return 0; } |
Compliant Solution
In this compliant solution, the function do_xyz()
is invoked and the return value is compared to 0.:
Code Block | ||||
---|---|---|---|---|
| ||||
int do_xyz(void); int f(void) { /* ... */ if (do_xyz()) { return -1; /* handle errorIndicate failure */ } /* ... */ return 0; } |
Risk Assessment
Errors of omission can result in unintended program flow.
Recommendation | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
EXP16-C |
Low |
Likely |
Medium | P6 | L2 |
Automated Detection
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Astrée |
| function-name-constant-comparison | Partially checked | ||||||
| BAD_COMPARE | Can detect the specific instance where the address of a function is compared against 0, such as in the case of | |||||||
GCC |
| Can detect violations of this recommendation when the | |||||||
Helix QAC |
| C0428, C3004, C3344 | |||||||
Klocwork |
| CWARN.NULLCHECK.FUNCNAME | |||||||
LDRA tool suite |
|
Can detect violations of this recommendation when the -Wall
flag is used.
EFFECT
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
...
...
...
24772:2013 | Likely incorrect expressions [KOA] |
ISO/IEC TS 17961 | Comparing function addresses to zero [funcaddr] |
ISO/IEC TR 24772 "KOA Likely incorrect expressions"
...
...
480, |
...
Use of incorrect operator CWE-482, Comparing instead of assigning |
Bibliography
[Hatton 1995] | Section 2.7.2, "Errors of |
...
Omission and |
...
Addition" |
...