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: 8 rules found
privacy
    Impact
      Clean code attribute
        1. JWT should be signed and verified with strong cipher algorithms

           Vulnerability
        2. Cipher algorithms should be robust

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

           Vulnerability
        4. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        5. Cryptographic keys should be robust

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

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

           Security Hotspot
        8. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot

        Creating cookies without the "secure" flag is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe
        • privacy

        When a cookie is protected with the secure attribute set to true it will not be send by the browser over an unencrypted HTTP request and thus cannot be observed by an unauthorized person during a man-in-the-middle attack.

        Ask Yourself Whether

        • the cookie is for instance a session-cookie not designed to be sent over non-HTTPS communication.
        • it’s not sure that the website contains mixed content or not (ie HTTPS everywhere or not)

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

        Recommended Secure Coding Practices

        • It is recommended to use HTTPs everywhere so setting the secure flag to true should be the default behaviour when creating cookies.
        • Set the secure flag to true for session-cookies.

        Sensitive Code Example

        When the HttpCookie.Secure property is set to false then the cookie will be send during an unencrypted HTTP request:

        HttpCookie myCookie = new HttpCookie("Sensitive cookie");
        myCookie.Secure = false; //  Sensitive: a security-sensitive cookie is created with the secure flag set to false
        

        The default value of Secure flag is false, unless overwritten by an application’s configuration file:

        HttpCookie myCookie = new HttpCookie("Sensitive cookie");
        //  Sensitive: a security-sensitive cookie is created with the secure flag not defined (by default set to false)
        

        Compliant Solution

        Set the HttpCookie.Secure property to true:

        HttpCookie myCookie = new HttpCookie("Sensitive cookie");
        myCookie.Secure = true; // Compliant
        

        Or change the default flag values for the whole application by editing the Web.config configuration file:

        <httpCookies httpOnlyCookies="true" requireSSL="true" />
        
        • the requireSSL attribute corresponds programmatically to the Secure field.
        • the httpOnlyCookies attribute corresponds programmatically to the httpOnly field.

        See

        • OWASP - Top 10 2021 Category A4 - Insecure Design
        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • CWE - CWE-311 - Missing Encryption of Sensitive Data
        • CWE - CWE-315 - Cleartext Storage of Sensitive Information in a Cookie
        • CWE - CWE-614 - Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
        • STIG Viewer - Application Security and Development: V-222576 - The application must set the secure flag on session cookies.
          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