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

        Use model binding instead of reading raw request data

        adaptability - focused
        maintainability
        reliability
        security
        Code Smell
        • asp.net

        The HttpRequest class provides access to the raw request data through the QueryString, Headers, and Forms properties. However, whenever possible it is recommended to use model binding instead of directly accessing the input data.

        Why is this an issue?

        How can I fix it?

        More Info

        Both ASP.Net MVC implementations - Core and Framework - support model binding in a comparable fashion. Model binding streamlines the process by automatically aligning data from HTTP requests with action method parameters, providing numerous benefits compared to manually parsing raw incoming request data:

        Simplicity

        Model binding simplifies the code by automatically mapping data from HTTP requests to action method parameters. You don’t need to write any code to manually extract values from the request.

        Type Safety

        Model binding provides type safety by automatically converting the incoming data into the appropriate .NET types. If the conversion fails, the model state becomes invalid, which you can easily check using ModelState.IsValid.

        Validation

        With model binding, you can easily apply validation rules to your models using data annotations. If the incoming data doesn’t comply with these rules, the model state becomes invalid.

        Security

        Model binding helps protect against over-posting attacks by only including properties in the model that you explicitly bind using the [Bind] attribute or by using view models that only contain the properties you want to update.

        Maintainability

        By using model binding, your code becomes cleaner, easier to read, and maintain. It promotes the use of strongly typed views, which can provide compile-time checking of your views.

          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
          10.6
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.6

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use