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.TAINT.PATH : Tainted Path (C#)

Summary

Tainted data flows into a field annotated as [PathTrusted], or into a file path creation method.

See the OWASP page on Path Traversal 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 Tainted Path (C#)
Significance security
Mnemonic CSHARP.IO.TAINT.PATH
Categories
CWE CWE:22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
OWASP-2017 OWASP-2017:A1 Injection
  OWASP-2017:A5 Broken access control
OWASP-2021 OWASP-2021:A1 Broken access control
  OWASP-2021:A3 Injection
  OWASP-2021:A4 Insecure design
OWASP-2025 OWASP-2025:A01 Broken Access Control
  OWASP-2025:A05 Injection
  OWASP-2025:A06 Insecure Design
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="Tainted Path (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 prepared statements for SQL queries rather than free queries built from string concatenation.

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