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

           Vulnerability
        2. Content Security Policies should be restrictive

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

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

           Code Smell
        5. JWT secret keys should not be disclosed

           Vulnerability
        6. Stack traces should not be disclosed

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

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

           Vulnerability
        9. Using unsafe code blocks is security-sensitive

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

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

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

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

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

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

           Vulnerability
        16. XML signatures should be validated securely

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

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

           Vulnerability
        19. Reflection should not be vulnerable to injection attacks

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

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

           Vulnerability
        22. Types allowed to be deserialized should be restricted

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

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

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

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

           Vulnerability
        27. Cipher algorithms should be robust

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

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

           Vulnerability
        30. Using publicly writable directories is security-sensitive

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

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

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

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

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

           Vulnerability
        36. Logging should not be vulnerable to injection attacks

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

           Vulnerability
        38. Deserialization should not be vulnerable to injection attacks

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

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

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

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

           Vulnerability
        43. Configuring loggers is security-sensitive

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

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

           Security Hotspot
        46. Disabling CSRF protections is security-sensitive

           Security Hotspot
        47. LDAP connections should be authenticated

           Vulnerability
        48. Cryptographic keys should be robust

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

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

           Vulnerability
        51. Serialization constructors should be secured

           Vulnerability
        52. Members should not have conflicting transparency annotations

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

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

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

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

           Security Hotspot
        57. Cipher Block Chaining IVs should be unpredictable

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

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

           Vulnerability
        60. Setting loose file permissions is security-sensitive

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

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

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

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

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

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

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

           Vulnerability
        68. Formatting SQL queries is security-sensitive

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

           Vulnerability
        70. Hard-coded credentials are security-sensitive

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

           Vulnerability
        72. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        A secure password should be used when connecting to a database

        responsibility - trustworthy
        security
        Vulnerability
        • cwe

        When accessing a database, an empty password should be avoided as it introduces a weakness.

        Why is this an issue?

        How can I fix it?

        More Info

        When a database does not require a password for authentication, it allows anyone to access and manipulate the data stored within it. Exploiting this vulnerability typically involves identifying the target database and establishing a connection to it without the need for any authentication credentials.

        What is the potential impact?

        Once connected, an attacker can perform various malicious actions, such as viewing, modifying, or deleting sensitive information, potentially leading to data breaches or unauthorized access to critical systems. It is crucial to address this vulnerability promptly to ensure the security and integrity of the database and the data it contains.

        Unauthorized Access to Sensitive Data

        When a database lacks a password for authentication, it opens the door for unauthorized individuals to gain access to sensitive data. This can include personally identifiable information (PII), financial records, intellectual property, or any other confidential information stored in the database. Without proper access controls in place, malicious actors can exploit this vulnerability to retrieve sensitive data, potentially leading to identity theft, financial loss, or reputational damage.

        Compromise of System Integrity

        Without a password requirement, unauthorized individuals can gain unrestricted access to a database, potentially compromising the integrity of the entire system. Attackers can inject malicious code, alter configurations, or manipulate data within the database, leading to system malfunctions, unauthorized system access, or even complete system compromise. This can disrupt business operations, cause financial losses, and expose the organization to further security risks.

        Unwanted Modifications or Deletions

        The absence of a password for database access allows anyone to make modifications or deletions to the data stored within it. This poses a significant risk, as unauthorized changes can lead to data corruption, loss of critical information, or the introduction of malicious content. For example, an attacker could modify financial records, tamper with customer orders, or delete important files, causing severe disruptions to business processes and potentially leading to financial and legal consequences.

        Overall, the lack of a password configured to access a database poses a serious security risk, enabling unauthorized access, data breaches, system compromise, and unwanted modifications or deletions. It is essential to address this vulnerability promptly to safeguard sensitive data, maintain system integrity, and protect the organization from potential harm.

          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