SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
C#

C# static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C# code

  • All rules 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
Filtered: 26 rules found
injection
    Impact
      Clean code attribute
        1. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        2. Stack traces should not be disclosed

           Vulnerability
        3. Loop boundaries should not be vulnerable to injection attacks

           Vulnerability
        4. Connection strings should not be vulnerable to injections attacks

           Vulnerability
        5. Memory allocations should not be vulnerable to Denial of Service attacks

           Vulnerability
        6. Accessing files should not lead to filesystem oracle attacks

           Vulnerability
        7. Environment variables should not be defined from untrusted input

           Vulnerability
        8. XML operations should not be vulnerable to injection attacks

           Vulnerability
        9. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        10. Applications should not create session cookies from untrusted input

           Vulnerability
        11. Reflection should not be vulnerable to injection attacks

           Vulnerability
        12. Extracting archives should not lead to zip slip vulnerabilities

           Vulnerability
        13. OS commands should not be vulnerable to argument injection attacks

           Vulnerability
        14. Dynamic code execution should not be vulnerable to injection attacks

           Vulnerability
        15. NoSQL operations should not be vulnerable to injection attacks

           Vulnerability
        16. HTTP request redirections should not be open to forging attacks

           Vulnerability
        17. Logging should not be vulnerable to injection attacks

           Vulnerability
        18. Server-side requests should not be vulnerable to forging attacks

           Vulnerability
        19. Deserialization should not be vulnerable to injection attacks

           Vulnerability
        20. Endpoints should not be vulnerable to reflected cross-site scripting (XSS) attacks

           Vulnerability
        21. Database queries should not be vulnerable to injection attacks

           Vulnerability
        22. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        23. XPath expressions should not be vulnerable to injection attacks

           Vulnerability
        24. I/O function calls should not be vulnerable to path injection attacks

           Vulnerability
        25. LDAP queries should not be vulnerable to injection attacks

           Vulnerability
        26. OS commands should not be vulnerable to command injection attacks

           Vulnerability

        XML operations should not be vulnerable to injection attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        XML injections occur when an application builds an XML-formatted string from user input without prior validation or sanitation. In such a case, a tainted user-controlled value can tamper with the XML string content. Especially, unexpected arbitrary elements and attributes can be inserted in the corresponding XML description.

        A malicious injection payload could, for example:

        • Insert tags into the main XML document.
        • Add attributes to an existing XML tag.
        • Change the data value inside a tag.

        A malicious user-supplied value can perform other modifications depending on where and how the constructed data is later used.

        What is the potential impact?

        The consequences of an XML injection attack on an application vary greatly depending on the application’s logic. It can affect the application itself or another element if the XML document is used for cross-component data exchange. For this reason, the actual impact can range from benign information disclosure to critical remote code execution.

        Information disclosure

        An attacker can forge an attack payload that will modify the XML document so that it will become syntactically incorrect. In that case, when the data is later used, the parsing component will raise a technical error. If displayed back to the attacker or made available through log files, this technical error may disclose sensitive business or technical information.

        This scenario, while in general the less severe one, is the most frequently encountered. It can combine with any other logic-dependant threat.

        Internal requests tampering

        Some applications communicate with backend micro-services APIs using XML-based protocols such as SOAP. When those applications are vulnerable to XML injections, attackers can tamper with the internal requests' content. This will allow them to change internal requests' parameters or locations which, in turn, can lead to various consequences like performing unauthorized actions or accessing sensitive data.

        For example, altering a user creation request in such a way can lead to a privilege escalation if attackers manage to modify the default account privilege level.

        Code execution

        An application might build objects based on an XML serialization string. In that case, an attacker that would exploit an XML injection could be able to alter the serialization string to modify the corresponding object’s properties.

        Depending on the deserialization process, this might allow instantiating arbitrary objects or objects with sensitive properties altered. This can lead to arbitrary code being executed in the same way as a deserialization injection vulnerability.

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.3

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use