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

        Reflection 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

        Reflection injections occur in a web application when it retrieves data from a user or a third-party service and fully or partially uses it to inspect, load or invoke a component by name.

        If an application uses a reflection method in a way that is vulnerable to injections, it is exposed to attacks that aim to achieve remote code execution on the server’s website.

        A user with malicious intent exploits this by carefully crafting a string involving symbols such as class methods, that will help them change the initial reflection logic to an impactful malicious one.

        After creating the malicious request and triggering it, the attacker can attack the servers affected by this vulnerability without relying on any pre-requisites.

        What is the potential impact?

        If user-supplied values are used to choose which code is executed, an attacker may be able to supply carefully-chosen values that cause unexpected code to run. The attacker can use this ability to run arbitrary code on the server.

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

        Application-specific attacks

        In this scenario, the attackers succeed in injecting a seemingly-legitimate object, but whose properties might be used maliciously.

        Depending on the application, attackers might be able to modify important data structures or content to escalate privileges or perform unwanted actions. For example, with an e-commerce application, this could be changing the number of products or prices.

        Full application compromise

        In the worst-case scenario, the attackers succeed in injecting an object triggering code execution.

        Depending on the attacker, code execution can be used with different intentions:

        • Download the internal server’s data, most likely to sell it.
        • Modify data, install malware, for instance, malware that mines cryptocurrencies.
        • Stop services or exhaust resources, for instance, with fork bombs.

        This threat is particularly insidious if the attacked organization does not maintain a Disaster Recovery Plan (DRP).

        Root privilege escalation and pivot

        In this scenario, the attacker can do everything described in the previous section. The difference is that the attacker additionally manages to elevate their privileges as an administrator and attack other servers.

        Here, the impact depends on how much the target company focuses on its Defense In Depth. For example, the entire infrastructure can be compromised through a combination of unsafe deserialization and misconfiguration:

        • Docker or Kubernetes clusters
        • cloud services
        • network firewalls and routing
        • OS access control
          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