JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

CodeSonar® 9.2p0 CONFIDENTIAL CodeSecure Inc
C and C++
Binaries


IO.INJ.COMMAND : Command Injection

Summary

Potentially-tainted data is used to construct an operating system command.

Properties

Class Name Command Injection
Significance security
Mnemonic IO.INJ.COMMAND
Categories
MisraC2025 MisraC2025:D.4.14 The validity of values received from external sources shall be checked
MisraC2023 MisraC2023:D.4.14 The validity of values received from external sources shall be checked
Misra2012 Misra2012:D.4.14 The validity of values received from external sources shall be checked
AUTOSARC++14 AUTOSARC++14:A27-0-1 Inputs from independent components shall be validated.
MisraC++2023 MisraC++2023:0.3.2 A function call shall not violate the function's preconditions
CWE CWE:78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
  CWE:88 Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
  CWE:114 Process Control
CERT-C CERT-C:ENV33-C Do not call system()
  CERT-C:STR02-C Sanitize data passed to complex subsystems
DISA-6r1 DISA-6r1:V-222604 The application must protect from command injection.
  DISA-6r1:V-222606 The application must validate all input.
DISA-5r3 DISA-5r3:V-70261 The application must protect from command injection.
  DISA-5r3:V-70265 The application must validate all input.
DISA-4r3 DISA-4r3:V-70261 The application must protect from command injection.
  DISA-4r3:V-70265 The application must validate all input.
DISA-3r10 DISA-3r10:V-6164 The designer will ensure the application validates all input.
  DISA-3r10:V-16810 The designer will ensure the application does not allow command injection.
OWASP-2017 OWASP-2017:A1 Injection
OWASP-2021 OWASP-2021:A3 Injection
OWASP-2025 OWASP-2025:A05 Injection
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="Command Injection"

Example

#include <stdlib.h>
#include <stdio.h>

int command_from_file(FILE *infile)
{
    char comm[80];
    char *res = fgets(comm, 80, infile);
    if (res)
        return system(comm); /* 'Command Injection' warning issued here */
    return -1;
}

Triggers

CodeSonar ships with library models that allow it to recognize a number of functions that use one or more of their parameters to construct an operating system command. Some examples are shown in the table below. If one of these functions is called with a tainted value in one of those parameter positions, 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 Command Injection warnings.

Functions that can trigger warnings include...
gcc Builtins __builtin_execl(), __builtin_execle()
libc execv(), popen(), system()
Win32 CreateProcessA(), CreateProcessW(), _wsystem()

Relevant Configuration File Parameters

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

 

To report problems with this documentation, please visit https://support.codesecure.com/.