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: 4 rules found
denial-of-service
    Impact
      Clean code attribute
        1. Classes should "Dispose" of members from the classes' own "Dispose" methods

           Bug
        2. Classes with "IDisposable" members should implement "IDisposable"

           Bug
        3. "IDisposables" should be disposed

           Bug
        4. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability

        "IDisposables" should be disposed

        intentionality - logical
        reliability
        Bug
        • cwe
        • denial-of-service

        Why is this an issue?

        How can I fix it?

        More Info

        When writing managed code, there is no need to worry about memory allocation or deallocation as it is taken care of by the garbage collector. However, certain objects, such as Bitmap, utilize unmanaged memory for specific purposes like pointer arithmetic. These objects may have substantial unmanaged memory footprints while having minimal managed footprints. Unfortunately, the garbage collector only recognizes the small managed footprint and does not promptly reclaim the corresponding unmanaged memory (by invoking the finalizer method of Bitmap) for efficiency reasons.

        In addition, it’s essential to manage other system resources besides memory. The operating system has limits on the number of file descriptors (e.g., FileStream) or sockets (e.g., WebClient) that can remain open simultaneously. Therefore, it’s crucial to Dispose of these resources promptly when they are no longer required, instead of relying on the garbage collector to invoke the finalizers of these objects at an unpredictable time in the future.

        This rule keeps track of private fields and local variables of specific types that implement IDisposable or IAsyncDisposable. It identifies instances of these types that are not properly disposed, closed, aliased, returned, or passed to other methods. This applies to instances that are either directly created using the new operator or instantiated through a predefined list of factory methods.

        Here is the list of the types tracked by this rule:

        • FluentAssertions.Execution.AssertionScope
        • System.Drawing.Bitmap
        • System.Drawing.Image
        • System.IO.FileStream
        • System.IO.StreamReader
        • System.IO.StreamWriter
        • System.Net.Sockets.TcpClient
        • System.Net.Sockets.UdpClient
        • System.Net.WebClient

        Here is the list of predefined factory methods tracked by this rule:

        • System.Drawing.Image.FromFile()
        • System.Drawing.Image.FromStream()
        • System.IO.File.Create()
        • System.IO.File.Open()

        Exceptions

        IDisposable / IAsyncDisposable variables returned from a method or passed to other methods are ignored, as are local IDisposable / IAsyncDisposable objects that are initialized with other IDisposable / IAsyncDisposable objects.

        public Stream WriteToFile(string path, string text)
        {
          var fs = new FileStream(path, FileMode.Open); // Compliant: it is returned
          var bytes = Encoding.UTF8.GetBytes(text);
          fs.Write(bytes, 0, bytes.Length);
          return fs;
        }
        
        public void ReadFromStream(Stream s)
        {
          var sr = new StreamReader(s); // Compliant: it would close the underlying stream.
          // ...
        }
        
          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