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 "HttpOnly" flag is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe
        • privacy

        When a cookie is configured with the HttpOnly attribute set to true, the browser guaranties that no client-side script will be able to read it. In most cases, when a cookie is created, the default value of HttpOnly is false and it’s up to the developer to decide whether or not the content of the cookie can be read by the client-side script. As a majority of Cross-Site Scripting (XSS) attacks target the theft of session-cookies, the HttpOnly attribute can help to reduce their impact as it won’t be possible to exploit the XSS vulnerability to steal session-cookies.

        Ask Yourself Whether

        • the cookie is sensitive, used to authenticate the user, for instance a session-cookie
        • the HttpOnly attribute offer an additional protection (not the case for an XSRF-TOKEN cookie / CSRF token for example)

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

        Recommended Secure Coding Practices

        • By default the HttpOnly flag should be set to true for most of the cookies and it’s mandatory for session / sensitive-security cookies.

        Sensitive Code Example

        When the HttpCookie.HttpOnly property is set to false then the cookie can be accessed by client side code:

        HttpCookie myCookie = new HttpCookie("Sensitive cookie");
        myCookie.HttpOnly = false; // Sensitive: this cookie is created with the httponly flag set to false and so it can be stolen easily in case of XSS vulnerability
        

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

        HttpCookie myCookie = new HttpCookie("Sensitive cookie");
        // Sensitive: this cookie is created without the httponly flag  (by default set to false) and so it can be stolen easily in case of XSS vulnerability
        

        Compliant Solution

        Set the HttpCookie.HttpOnly property to true:

        HttpCookie myCookie = new HttpCookie("Sensitive cookie");
        myCookie.HttpOnly = true; // Compliant: the sensitive cookie is protected against theft thanks to the HttpOnly property set to true (HttpOnly = true)
        

        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 A5 - Security Misconfiguration
        • OWASP HttpOnly
        • OWASP - Top 10 2017 Category A7 - Cross-Site Scripting (XSS)
        • CWE - CWE-1004 - Sensitive Cookie Without 'HttpOnly' Flag
        • Derived from FindSecBugs rule HTTPONLY_COOKIE
        • STIG Viewer - Application Security and Development: V-222575 - The application must set the HTTPOnly 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