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

        Regular expressions should not be vulnerable to Denial of Service attacks

        intentionality - efficient
        security
        Vulnerability
        • cwe
        • denial-of-service
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Regular expression injections occur when the application retrieves untrusted data and uses it as a regex to pattern match a string with it.

        Most regular expression search engines use backtracking to try all possible regex execution paths when evaluating an input. Sometimes this can lead to performance problems also referred to as catastrophic backtracking situations.

        What is the potential impact?

        In the context of a web application vulnerable to regex injection:
        After discovering the injection point, attackers insert data into the vulnerable field to make the affected component inaccessible.

        Depending on the application’s software architecture and the injection point’s location, the impact may or may not be visible.

        Below are some real-world scenarios that illustrate some impacts of an attacker exploiting the vulnerability.

        Self Denial of Service

        In cases where the complexity of the regular expression is exponential to the input size, a small, carefully-crafted input (for example, 20 chars) can trigger catastrophic backtracking and cause a denial of service of the application.

        Super-linear regex complexity can produce the same effects for a large, carefully crafted input (thousands of chars).

        If the component jeopardized by this vulnerability is not a bottleneck that acts as a single point of failure (SPOF) within the application, the denial of service might only affect the attacker who initiated it.

        Such benign denial of service can also occur in architectures that rely heavily on containers and container orchestrators. Replication systems would detect the failure of a container and automatically replace it.

        Infrastructure SPOFs

        However, a denial of service attack can be critical to the enterprise if it targets a SPOF component. Sometimes the SPOF is a software architecture vulnerability (such as a single component on which multiple critical components depend) or an operational vulnerability (for example, insufficient container creation capabilities or failures from containers to terminate).

        In either case, attackers aim to exploit the infrastructure weakness by sending as many malicious payloads as possible, using potentially huge offensive infrastructures.

        These threats are particularly insidious if the attacked organization does not maintain a disaster recovery plan (DRP).

          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
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use