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.UT.PROC : Untrusted Process Creation

Summary

A process creation function is called with an untrusted process name argument.

A process name argument is considered to be untrusted if:

Properties

Class Name Untrusted Process Creation
Significance security
Mnemonic IO.UT.PROC
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')
CERT-C 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.
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 disabled by default. To enable them, add the following WARNING_FILTER rule to the project configuration file.
WARNING_FILTER += allow class="Untrusted Process Creation"

Triggers

CodeSonar ships with library models that allow it to recognize functions such as libc execv() and Win32 CreateProcessA() that take a process name argument. If one of these functions is called with an untrusted value in the process name 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 Untrusted Process Creation warnings.

Example

Suppose the project configuration file contains the following rule (this is part of the factory settings for UNTRUSTED_PROC_BLACKLIST).

UNTRUSTED_PROC_BLACKLIST += ^\s*(.*[/\\])?(a|ba|c|k|pdk|sc|tc|z)?sh(\s+.*)*$

Then CodeSonar will issue one Untrusted Process Creation warning in the following code.

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


void ut_proc(const char *command)
{
    FILE *pipe_file;

    /* "/usr/bin/myprocess" does not match UNTRUSTED_PROC_BLACKLIST rule */
    if (pipe_file = (FILE*)popen("/usr/bin/myprocess","r")){
      /* ... */
      pclose(pipe_file);
    }

    /* "/usr/bin/sh" forbidden by UNTRUSTED_PROC_BLACKLIST setting */
    if (pipe_file = (FILE*)popen("/usr/bin/sh","r")){ /* 'Untrusted Process Creation' warning issued here */
      /* ... */
      pclose(pipe_file);
    }
}

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/.