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: 90 rules found
cwe
    Impact
      Clean code attribute
        1. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        2. JWT secret keys 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. Blocks should not be synchronized on local variables

           Bug
        9. Not specifying a timeout for regular expressions is security-sensitive

           Security Hotspot
        10. Hard-coded secrets are security-sensitive

           Security Hotspot
        11. XML operations should not be vulnerable to injection attacks

           Vulnerability
        12. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        13. Applications should not create session cookies from untrusted input

           Vulnerability
        14. Reflection should not be vulnerable to injection attacks

           Vulnerability
        15. Extracting archives should not lead to zip slip vulnerabilities

           Vulnerability
        16. OS commands should not be vulnerable to argument injection attacks

           Vulnerability
        17. Types allowed to be deserialized should be restricted

           Vulnerability
        18. Deserializing objects without performing data validation is security-sensitive

           Security Hotspot
        19. Disabling ASP.NET "Request Validation" feature is security-sensitive

           Security Hotspot
        20. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        21. JWT should be signed and verified with strong cipher algorithms

           Vulnerability
        22. Cipher algorithms should be robust

           Vulnerability
        23. Encryption algorithms should be used with secure mode and padding scheme

           Vulnerability
        24. Insecure temporary file creation methods should not be used

           Vulnerability
        25. Using publicly writable directories is security-sensitive

           Security Hotspot
        26. Passwords should not be stored in plaintext or with a fast hashing algorithm

           Vulnerability
        27. Dynamic code execution should not be vulnerable to injection attacks

           Vulnerability
        28. Using clear-text protocols is security-sensitive

           Security Hotspot
        29. NoSQL operations should not be vulnerable to injection attacks

           Vulnerability
        30. HTTP request redirections should not be open to forging attacks

           Vulnerability
        31. Logging should not be vulnerable to injection attacks

           Vulnerability
        32. Server-side requests should not be vulnerable to forging attacks

           Vulnerability
        33. Deserialization should not be vulnerable to injection attacks

           Vulnerability
        34. Endpoints should not be vulnerable to reflected cross-site scripting (XSS) attacks

           Vulnerability
        35. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        36. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        37. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        38. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        39. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        40. Disabling CSRF protections is security-sensitive

           Security Hotspot
        41. Unread "private" fields should be removed

           Code Smell
        42. LDAP connections should be authenticated

           Vulnerability
        43. Cryptographic keys should be robust

           Vulnerability
        44. Weak SSL/TLS protocols should not be used

           Vulnerability
        45. Secure random number generators should not output predictable values

           Vulnerability
        46. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        47. Empty nullable value should not be accessed

           Bug
        48. Database queries should not be vulnerable to injection attacks

           Vulnerability
        49. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        50. Cipher Block Chaining IVs should be unpredictable

           Vulnerability
        51. Classes should "Dispose" of members from the classes' own "Dispose" methods

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

           Bug
        53. "IDisposables" should be disposed

           Bug
        54. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        55. Multiline blocks should be enclosed in curly braces

           Code Smell
        56. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        57. Setting loose file permissions is security-sensitive

           Security Hotspot
        58. Boolean expressions should not be gratuitous

           Code Smell
        59. Conditionally executed code should be reachable

           Bug
        60. Generic exceptions should not be ignored

           Code Smell
        61. Blocks should be synchronized on read-only fields

           Bug
        62. Mutable fields should not be "public static"

           Code Smell
        63. Null pointers should not be dereferenced

           Bug
        64. Using non-standard cryptographic algorithms is security-sensitive

           Security Hotspot
        65. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        66. "ToString()" method should not return null

           Bug
        67. Locks should be released on all paths

           Bug
        68. "Exception" should not be caught

           Code Smell
        69. Results of integer division should not be assigned to floating point variables

           Bug
        70. A secure password should be used when connecting to a database

           Vulnerability
        71. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        72. XPath expressions should not be vulnerable to injection attacks

           Vulnerability
        73. I/O function calls should not be vulnerable to path injection attacks

           Vulnerability
        74. LDAP queries should not be vulnerable to injection attacks

           Vulnerability
        75. Formatting SQL queries is security-sensitive

           Security Hotspot
        76. OS commands should not be vulnerable to command injection attacks

           Vulnerability
        77. Hard-coded credentials are security-sensitive

           Security Hotspot
        78. Password hashing functions should use an unpredictable salt

           Vulnerability
        79. Invalid casts should be avoided

           Code Smell
        80. Unused assignments should be removed

           Code Smell
        81. "==" should not be used when "Equals" is overridden

           Code Smell
        82. NullReferenceException should not be caught

           Code Smell
        83. "switch/Select" statements should contain a "default/Case Else" clauses

           Code Smell
        84. "Equals(Object)" and "GetHashCode()" should be overridden in pairs

           Bug
        85. Exit methods should not be called

           Code Smell
        86. Track uses of "TODO" tags

           Code Smell
        87. Track uses of "FIXME" tags

           Code Smell
        88. Assignments should not be made from within sub-expressions

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

           Code Smell
        90. Fields should not have public accessibility

           Code Smell

        Using pseudorandom number generators (PRNGs) is security-sensitive

        responsibility - trustworthy
        security
        Security Hotspot
        • cwe

        PRNGs are algorithms that produce sequences of numbers that only approximate true randomness. While they are suitable for applications like simulations or modeling, they are not appropriate for security-sensitive contexts because their outputs can be predictable if the internal state is known.

        In contrast, cryptographically secure pseudorandom number generators (CSPRNGs) are designed to be secure against prediction attacks. CSPRNGs use cryptographic algorithms to ensure that the generated sequences are not only random but also unpredictable, even if part of the sequence or the internal state becomes known. This unpredictability is crucial for security-related tasks such as generating encryption keys, tokens, or any other values that must remain confidential and resistant to guessing attacks.

        For example, the use of non-cryptographic PRNGs has led to vulnerabilities such as:

        • CVE-2013-6386
        • CVE-2006-3419
        • CVE-2008-4102

        When software generates predictable values in a context requiring unpredictability, it may be possible for an attacker to guess the next value that will be generated, and use this guess to impersonate another user or access sensitive information. Therefore, it is critical to use CSPRNGs in any security-sensitive application to ensure the robustness and security of the system.

        As the System.Random class relies on a non-cryptographic pseudorandom number generator, it should not be used for security-critical applications or for protecting sensitive data. In such context, the System.Cryptography.RandomNumberGenerator class which relies on a CSPRNG should be used in place.

        Ask Yourself Whether

        • the code using the generated value requires it to be unpredictable. It is the case for all encryption mechanisms or when a secret value, such as a password, is hashed.
        • the function you use is a non-cryptographic PRNG.
        • the generated value is used multiple times.
        • an attacker can access the generated value.

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

        Recommended Secure Coding Practices

        • Only use random number generators which are recommended by OWASP or any other trusted organization.
        • Use the generated random values only once.
        • You should not expose the generated random value. If you have to store it, make sure that the database or file is secure.

        Sensitive Code Example

        var random = new Random(); // Sensitive use of Random
        byte[] data = new byte[16];
        random.NextBytes(data);
        return BitConverter.ToString(data); // Check if this value is used for hashing or encryption
        

        Compliant Solution

        using System.Security.Cryptography;
        ...
        var randomGenerator = RandomNumberGenerator.Create();
        byte[] data = new byte[16];
        randomGenerator.GetBytes(data);
        return BitConverter.ToString(data);
        

        See

        • OWASP - Secure Random Number Generation Cheat Sheet
        • OWASP - Top 10 2021 Category A2 - Cryptographic Failures
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • CWE - CWE-338 - Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
        • CWE - CWE-330 - Use of Insufficiently Random Values
        • CWE - CWE-326 - Inadequate Encryption Strength
        • CWE - CWE-1241 - Use of Predictable Algorithm in Random Number Generator
          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