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#


CSHARP.IO.INJ.COMMAND : Command Injection (C#)

Summary

Tainted data flows into a field annotated as [CommandTrusted], or into a command execution routine.

See the OWASP page on Command Injection for more information.

Checks for this class use the CodeSonar C# taint analysis. See Taint Tracking for CodeSonar C# Warning Classes for more information on this analysis, including lists of the methods that CodeSonar automatically recognizes as relevant and information about specifying additional methods that CodeSonar should recognize as taint sources, sinks, or sanitizers.

Use configuration parameter CSHARP_ANALYSIS_ADVANCED_INJECTION to specify the level of checking to perform for this and other taint-related warning classes:

Properties

Class Name Command Injection (C#)
Significance security
Mnemonic CSHARP.IO.INJ.COMMAND
Categories
CWE CWE:78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
DISA-6r1 DISA-6r1:V-222604 The application must protect from command injection.
DISA-5r3 DISA-5r3:V-70261 The application must protect from command injection.
DISA-4r3 DISA-4r3:V-70261 The application must protect from command injection.
OWASP-2017 OWASP-2017:A1 Injection
OWASP-2021 OWASP-2021:A3 Injection
OWASP-2025 OWASP-2025:A05 Injection
Availability Available for C# only.
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 (C#)"

Example

using System;
using System.IO;
using System.Net;

namespace DocumentationExample
{
    class OtherInjectionExamples
    {

        static void Main(string[] args)
        {
            string input = GetUserInput();

            CommandInjectionExample(input);
            PathInjectionExample(input);
            UrlInjectionExample(input);
        }

        private static String GetUserInput()
        {

            return Console.ReadLine();

        }

        private static void CommandInjectionExample(String input)
        {
            try
            {
                System.Diagnostics.Process.Start("CMD.exe", input); // Command Injection (C#) warning issued here 
            } catch (Exception e)
            {
                Console.WriteLine("invalid command: " + e.Message);
            }


        }

        private static void PathInjectionExample(string input)
        {
            try
            {
                File.Delete(input);                                 // Tainted Path (C#) warning issued here 
            } catch (Exception e)
            {
                Console.WriteLine("unable to delete file: " + e.Message);
            }
        }

        private static void UrlInjectionExample(String input)
        {

            try
            {
                WebRequest request = WebRequest.Create(input);      // Tainted URL (C#) warning issued here 
                // ...
 
                WebResponse response = request.GetResponse();

                using (Stream dataStream = response.GetResponseStream())
                {
                    StreamReader reader = new StreamReader(dataStream);
                    string responseFromServer = reader.ReadToEnd();
                    Console.WriteLine(responseFromServer);
                }

                response.Close();
            }
            catch (Exception e)
            {
                Console.WriteLine("request error: " + e.Message);
            }
        }
    }

}

Resolution

Verify that a security error actually corresponds to unconstrained information flow from source locations into sink locations. If this is the case, add a sanitizing algorithm to clean data before it flows into sinks, or use safe statements to propagate data inside the program.

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