 
                            ...
The following table shows a list of C standard library functions that provide limited or no error checking and reporting along with preferable alternatives:
| Function | Preferable | Comments | 
|---|---|---|
| 
 | 
 | No error indication, undefined behavior on error | 
| 
 | 
 | No error indication, undefined behavior on error | 
| 
 | 
 | No error indication, undefined behavior on error | 
| 
 | 
 | No error indication, undefined behavior on error | 
| 
 | 
 | No error indication, silent failure on error | 
| 
 | 
 | No error indication, silent failure on error | 
| ctime | asctime/localtime | Undefined behavior if  | 
Noncompliant Code Example (atoi())
...
| Code Block | ||||
|---|---|---|---|---|
| 
 | ||||
| int si;
if (argc > 1) {
  si = atoi(argv[1]);
}
 | 
The atoi(), atol(), and atoll() functions convert the initial portion of a string token to int, long int, and long long int representation respectively. Except for the behavior on error, they are equivalent as follows:
| Call | Equivalent on Success | 
|---|---|
| 
 | 
 | 
| 
 | 
 | 
| 
 | 
 | 
Unfortunately, atoi() and related functions lack a mechanism for reporting errors for invalid values. Specifically, the atoi(), atol(), and atoll() functions
- Do not need to set errnoon an error.
- Have BB. Definitions#undefined undefined behavior if the value of the result cannot be represented. (See CC. Undefined Behavior#ub_119 undefined behavior 118 of Annex J of the C Standard.)
- Return 0 if the string does not represent an integer (which is indistinguishable from a correctly formatted, zero-denoting input string), but the C Standard only specifies the behavior of these functions on success.
...
| Code Block | ||||
|---|---|---|---|---|
| 
 | ||||
| long sl;
int si;
char *end_ptr;
if (argc > 1) {
  errno = 0;
  sl = strtol(argv[1], &end_ptr, 10);
  if ((sl == LONG_MIN || sl == LONG_MAX)
   && errno != 0)
  {
    perror("strtol error");
  }
  else if (end_ptr == argv[1]) {
    if (puts("error encountered during conversion") == EOF) {
      /* Handle error */
    }
  }
  else if (sl > INT_MAX) {
    printf("%ld too large!\n", sl);
  }
  else if (sl < INT_MIN) {
    printf("%ld too small!\n", sl);
  }
  else if ('\0' != *end_ptr) {
    if (puts("extra characters on input line\n") == EOF) {
      /* Handle error */
    }
  }
  else {
    si = (int)sl;
  }
}
 | 
Both the noncompliant code example and the compliant solution are taken from INT06ERR34-C. Use strtol() or a related function to convert a string token to an integerDetect errors when converting a string to a number.
Noncompliant Code Example (rewind())
...
| Code Block | ||||
|---|---|---|---|---|
| 
 | ||||
| char *file_name;
FILE *fp;
/* Initialize file_name */
fp = fopen(file_name, "r");
if (fp == NULL) {
  /* Handle open error */
}
/* Read data */
rewind(fp);
/* Continue */
 | 
It is impossible to determine if rewind() succeeded.
...
| Code Block | ||||
|---|---|---|---|---|
| 
 | ||||
| char *file_name;
FILE *fp;
/* Initialize file_name */
fp = fopen(file_name, "r");
if (fp == NULL) {
  /* Handle open error */
}
/* Read data */
if (fseek(fp, 0L, SEEK_SET) != 0) {
  /* Handle repositioning error */
}
/* Continue */
 | 
Noncompliant Code Example (setbuf())
...
| Code Block | ||||
|---|---|---|---|---|
| 
 | ||||
| FILE *file;
/* Setup file */
setbuf(file, NULL);
/* ... */
 | 
It is not possible to determine if the call to setbuf() succeeded.
...
| Code Block | ||||
|---|---|---|---|---|
| 
 | ||||
| FILE *file;
char *buf = NULL;
/* Setup file */
if (setvbuf(file, buf, buf ? _IOFBF : _IONBF, BUFSIZ) != 0) {
  /* Handle error */
}
/* ... */
 | 
Risk Assessment
Although it is rare for a violation of this rule to result in a security BB. Definitions#vulnerability vulnerability, it can easily result in lost or misinterpreted data.
| Recommendation | Severity | Likelihood | 
|---|
| Detectable | Repairable | Priority | Level | 
|---|---|---|---|
| ERR07-C | Medium | Probable | Yes | 
| Yes | 
| P12 | 
| L1 | 
Automated Detection
This rule in general cannot be detected, although various examples can be detected by simply scanning for functions that have equivalent functions with better error handling.
| Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Astrée | 
 | bad-function | Fully checked | ||||||
| Axivion Bauhaus Suite | 
 | CertC-ERR07 | |||||||
| Helix QAC | 
 | C5046 | |||||||
| LDRA tool suite | 
 | 44 S, 593 S, 594 S | Partially implemented | ||||||
| Parasoft C/C++test | 
 | CERT_C-ERR07-a | The 'atof', 'atoi', 'atol' and 'atoll' functions from the 'stdlib.h' or 'cstdlib' library should not be used | ||||||
| PC-lint Plus | 
 | 586 | Fully supported | ||||||
| RuleChecker | 
 | bad-function | Fully checked | 
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
| MITRE CWE | CWE-20 | 
| , Improper Input Validation CWE-79, Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') CWE-89, Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') CWE-91, XML Injection (aka Blind XPath Injection) CWE-94, Improper Control of Generation of Code ('Code Injection') CWE-114, Process Control CWE-601, URL Redirection to Untrusted Site ('Open Redirect') CWE-676, Use of potentially dangerous function | 
Bibliography
...
...