C and C++ Binaries


IO.NEGFD : Negative file descriptor

Summary

An attempt to use a negative number as a file descriptor.

Properties

Class Name Negative file descriptor
Significance reliability
Mnemonic IO.NEGFD
Categories
MisraC2023 MisraC2023:D.4.1 Run-time failures shall be minimized
Misra2012 Misra2012:D.4.1 Run-time failures shall be minimized
CWE CWE:687 Function Call With Incorrectly Specified Argument Value
Availability Available for C and C++.
Enabling Checks for this warning class are enabled by default. To disable them, add the following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += discard class="Negative file descriptor"

Could Indicate

CWE:252 Unchecked Return Value

Example

#include <fcntl.h>
#include <unistd.h>

int negfd_nocheck(void){
  return close(open("myfile.txt",O_RDONLY)); /* 'Negative file descriptor' warning issued here
                                              *  - open() returns -1 on error
                                              */
}

int negfd_check(void){
  int rv;
  rv = open("myfile.txt",O_RDONLY);
  if (rv < 0){
    return -1;
  }
  return close(rv);
}

Triggering Functions

CodeSonar ships with library models that allow it to recognize a large number of functions that take a file descriptor or socket descriptor argument. Some examples are shown in the table below. If one of these functions is called with a negative value in the file/socket descriptor parameter position, a warning will be issued.

If you have created a custom library model for some function f() in terms of one of these existing models, calls to f() will also be capable of triggering Negative file descriptor warnings.

Functions that can trigger warnings include...
libc dup(), fdopen(), sendmsg(),
Win32 _dup(), _fstat64(), _write()

Relevant Configuration File Parameters

The following configuration file parameters affect checks for this warning class.