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: 17 rules found
error-handling
    Impact
      Clean code attribute
        1. Logging in a catch clause should pass the caught exception as a parameter.

           Code Smell
        2. Azure Functions should log all failures

           Code Smell
        3. Azure Functions should use Structured Error Handling

           Code Smell
        4. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        5. Exceptions should not be created without being thrown

           Bug
        6. Exception types should be "public"

           Code Smell
        7. Exceptions should not be explicitly rethrown

           Code Smell
        8. "catch" clauses should do more than rethrow

           Code Smell
        9. Generic exceptions should not be ignored

           Code Smell
        10. Exceptions should not be thrown from property getters

           Code Smell
        11. Overflow checking should not be disabled for "Enumerable.Sum"

           Code Smell
        12. "Exception" should not be caught

           Code Smell
        13. Classes named like "Exception" should extend "Exception" or a subclass

           Code Smell
        14. Exceptions should be either logged or rethrown but not both

           Code Smell
        15. NullReferenceException should not be caught

           Code Smell
        16. Exceptions should not be thrown in finally blocks

           Code Smell
        17. General or reserved exceptions should never be thrown

           Code Smell

        Delivering code in production with debug features activated is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe
        • error-handling
        • debug
        • user-experience

        Development tools and frameworks usually have options to make debugging easier for developers. Although these features are useful during development, they should never be enabled for applications deployed in production. Debug instructions or error messages can leak detailed information about the system, like the application’s path or file names.

        Ask Yourself Whether

        • The code or configuration enabling the application debug features is deployed on production servers or distributed to end users.
        • The application runs by default with debug features activated.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        Do not enable debugging features on production servers.

        The .Net Core framework offers multiple features which help during debug. Microsoft.AspNetCore.Builder.IApplicationBuilder.UseDeveloperExceptionPage and Microsoft.AspNetCore.Builder.IApplicationBuilder.UseDatabaseErrorPage are two of them. Make sure that those features are disabled in production.

        Use if (env.IsDevelopment()) to disable debug code.

        Sensitive Code Example

        This rule raises issues when the following .Net Core methods are called: Microsoft.AspNetCore.Builder.IApplicationBuilder.UseDeveloperExceptionPage, Microsoft.AspNetCore.Builder.IApplicationBuilder.UseDatabaseErrorPage.

        using Microsoft.AspNetCore.Builder;
        using Microsoft.AspNetCore.Hosting;
        
        namespace mvcApp
        {
            public class Startup2
            {
                public void Configure(IApplicationBuilder app, IHostingEnvironment env)
                {
                    // Those calls are Sensitive because it seems that they will run in production
                    app.UseDeveloperExceptionPage(); // Sensitive
                    app.UseDatabaseErrorPage(); // Sensitive
                }
            }
        }
        

        Compliant Solution

        using Microsoft.AspNetCore.Builder;
        using Microsoft.AspNetCore.Hosting;
        
        namespace mvcApp
        {
            public class Startup2
            {
                public void Configure(IApplicationBuilder app, IHostingEnvironment env)
                {
                    if (env.IsDevelopment())
                    {
                        // The following calls are ok because they are disabled in production
                        app.UseDeveloperExceptionPage(); // Compliant
                        app.UseDatabaseErrorPage(); // Compliant
                    }
                }
            }
        }
        

        Exceptions

        This rule does not analyze configuration files. Make sure that debug mode is not enabled by default in those files.

        See

        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • CWE - CWE-489 - Active Debug Code
        • CWE - CWE-215 - Information Exposure Through Debug Information
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • 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