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

        HTTP request redirections should not be open to forging attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Open redirection occurs when an application uses user-controllable data to redirect users to a URL.

        An attacker with malicious intent could manipulate a user to browse into a specially crafted URL, such as https://trusted.example.com?url=evil.example.com, to redirect the victim to his evil domain.

        Tricking users into sending the malicious HTTP request is usually the main task of exploiting an open redirection. Often, it requires an attacker to build a credible pretext to prevent suspicions from the victim.

        Attackers commonly use open redirect exploits in mass phishing campaigns.

        What is the potential impact?

        If an attacker tricks a user into opening a link of his choice, the user is redirected to a domain controlled by the attacker.

        From then on, the attacker can perform various malicious actions, some more impactful than others.

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

        Domain Mirroring

        A malicious link redirects to an attacker’s controlled website mirroring the interface of a web application trusted by the user. Due to the similarity in the application appearance and the apparently trustable clicked hyperlink, the user struggles to identify that they are browsing on a malicious domain.

        Depending on the attacker’s purpose, the malicious website can leak credentials, bypass Multi-Factor Authentication (MFA), and reach any authenticated data or action.

        Malware Distribution

        A malicious link redirects to an attacker’s controlled website that serves malware. On the same basis as the domain mirroring exploitation, the attacker develops a spearphishing or phishing campaign with a carefully crafted pretext that would result in the download and potential execution of a hosted malicious file.
        The worst-case scenario could result in complete system compromise.

          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