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
  • ShellShell
  • 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 494
  • Vulnerability47
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
Filtered: 73 rules found
Tags
    security
      Clean code attribute
        1. XSLT Transformations should not be vulnerable to injection attacks

           Vulnerability
        2. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        3. Content Security Policies should be restrictive

           Vulnerability
        4. ModelState.IsValid should be called in controller actions

           Code Smell
        5. Use model binding instead of reading raw request data

           Code Smell
        6. JWT secret keys should not be disclosed

           Vulnerability
        7. Stack traces should not be disclosed

           Vulnerability
        8. Loop boundaries should not be vulnerable to injection attacks

           Vulnerability
        9. Connection strings should not be vulnerable to injections attacks

           Vulnerability
        10. Using unsafe code blocks is security-sensitive

           Security Hotspot
        11. Memory allocations should not be vulnerable to Denial of Service attacks

           Vulnerability
        12. Accessing files should not lead to filesystem oracle attacks

           Vulnerability
        13. Environment variables should not be defined from untrusted input

           Vulnerability
        14. Not specifying a timeout for regular expressions is security-sensitive

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

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

           Vulnerability
        17. XML signatures should be validated securely

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

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

           Vulnerability
        20. Reflection should not be vulnerable to injection attacks

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

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

           Vulnerability
        23. Types allowed to be deserialized should be restricted

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

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

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

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

           Vulnerability
        28. Cipher algorithms should be robust

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

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

           Vulnerability
        31. Using publicly writable directories is security-sensitive

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

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

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

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

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

           Vulnerability
        37. Logging should not be vulnerable to injection attacks

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

           Vulnerability
        39. Deserialization should not be vulnerable to injection attacks

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

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

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

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

           Vulnerability
        44. Configuring loggers is security-sensitive

           Security Hotspot
        45. Using weak hashing algorithms is security-sensitive

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

           Security Hotspot
        47. Disabling CSRF protections is security-sensitive

           Security Hotspot
        48. LDAP connections should be authenticated

           Vulnerability
        49. Cryptographic keys should be robust

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

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

           Vulnerability
        52. Serialization constructors should be secured

           Vulnerability
        53. Members should not have conflicting transparency annotations

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

           Security Hotspot
        55. "CoSetProxyBlanket" and "CoInitializeSecurity" should not be used

           Vulnerability
        56. Database queries should not be vulnerable to injection attacks

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

           Security Hotspot
        58. Cipher Block Chaining IVs should be unpredictable

           Vulnerability
        59. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        60. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        61. Setting loose file permissions is security-sensitive

           Security Hotspot
        62. Using non-standard cryptographic algorithms is security-sensitive

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

           Security Hotspot
        64. A secure password should be used when connecting to a database

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

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

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

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

           Vulnerability
        69. Formatting SQL queries is security-sensitive

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

           Vulnerability
        71. Hard-coded credentials are security-sensitive

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

           Vulnerability
        73. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Weak SSL/TLS protocols should not be used

        responsibility - trustworthy
        security
        Vulnerability
        • cwe
        • privacy

        This vulnerability exposes encrypted data to a number of attacks whose goal is to recover the plaintext.

        Why is this an issue?

        How can I fix it?

        More Info

        Encryption algorithms are essential for protecting sensitive information and ensuring secure communications in a variety of domains. They are used for several important reasons:

        • Confidentiality, privacy, and intellectual property protection
        • Security during transmission or on storage devices
        • Data integrity, general trust, and authentication

        When selecting encryption algorithms, tools, or combinations, you should also consider two things:

        1. No encryption is unbreakable.
        2. The strength of an encryption algorithm is usually measured by the effort required to crack it within a reasonable time frame.

        For these reasons, as soon as cryptography is included in a project, it is important to choose encryption algorithms that are considered strong and secure by the cryptography community.

        To provide communication security over a network, SSL and TLS are generally used. However, it is important to note that the following protocols are all considered weak by the cryptographic community, and are officially deprecated:

        • SSL versions 1.0, 2.0 and 3.0
        • TLS versions 1.0 and 1.1

        When these unsecured protocols are used, it is best practice to expect a breach: that a user or organization with malicious intent will perform mathematical attacks on this data after obtaining it by other means.

        What is the potential impact?

        After retrieving encrypted data and performing cryptographic attacks on it on a given timeframe, attackers can recover the plaintext that encryption was supposed to protect.

        Depending on the recovered data, the impact may vary.

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

        Additional attack surface

        By modifying the plaintext of the encrypted message, an attacker may be able to trigger additional vulnerabilities in the code. An attacker can further exploit a system to obtain more information.
        Encrypted values are often considered trustworthy because it would not be possible for a third party to modify them under normal circumstances.

        Breach of confidentiality and privacy

        When encrypted data contains personal or sensitive information, its retrieval by an attacker can lead to privacy violations, identity theft, financial loss, reputational damage, or unauthorized access to confidential systems.

        In this scenario, the company, its employees, users, and partners could be seriously affected.

        The impact is twofold, as data breaches and exposure of encrypted data can undermine trust in the organization, as customers, clients and stakeholders may lose confidence in the organization’s ability to protect their sensitive data.

        Legal and compliance issues

        In many industries and locations, there are legal and compliance requirements to protect sensitive data. If encrypted data is compromised and the plaintext can be recovered, companies face legal consequences, penalties, or violations of privacy laws.

          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