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

        Connection strings should not be vulnerable to injections attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Database connection strings control how an application connects to a database. They include information such as the location of the database, how to authenticate with the database, and how the connection should be secured.

        The insertion of user-supplied values into a connection string can allow external control of these database connections.

        Why is this an issue?

        How can I fix it?

        More Info

        Connection strings contain a series of parameters that are structured as key/value pairs, similar to key1=value1;key2=value2.

        If an attacker can control values that are inserted into the connection string, they may be able to insert additional parameters. These additional parameters can override values that were supplied earlier in the connection string.

        What is the potential impact?

        An attacker can use specially-crafted values to change how the database connection is made. These values can add new parameters to the connection string, or can override parameters that had already been specified.

        Escalation of privilege

        Some database servers allow authentication via an OS user account instead of a username and password. The database connection is authenticated as the user running the application. When this authentication mode is used, any username or password in the connection string are ignored.

        If an attacker can force the use of this authentication mode, the connection will be made as the user that the web application is running under. This will often be the LocalSystem or NetworkService account on Windows. Such accounts are often given a high level of privileges on the database server.

        Credential theft

        If an attacker can change the database server in the connection string, they can have the web application connect to a server that they control. The web application will then authenticate with that server, allowing those credentials to be stolen.

        Bypassing data validation

        Many web applications implicitly trust data that’s stored in the database. The data is validated before it is stored, so no additional validation is performed when that data is loaded.

        If an attacker can change the database server in the connection string, they can have the web application connect to a database server that they control. Invalid data in this database could be passed to other services or systems, or could be used to trigger other bugs and logic flaws in the web application.

        Network traffic sniffing

        The connection string can control how the connection to the database server is secured. For example, it can control whether connections to Microsoft SQL Server use transport layer security (TLS).

        If an attacker can disable these network security measures and they have some way to monitor traffic between the web server and the database server, they will be able to see all information that’s written to and read from the database.

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

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use