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
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
Filtered: 9 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 hostnames should be verified during SSL/TLS connections

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

           Vulnerability
        6. Cryptographic keys should be robust

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

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

           Security Hotspot
        9. 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

        For Go Standard Library:

        import "net/http"
        
        func handler(w http.ResponseWriter, req *http.Request) {
            cookie := http.Cookie{}
            cookie.Name = "cookiename"
            cookie.Value = "cookievalue"
            http.SetCookie(w, &cookie) // Sensitive: HttpOnly is false by default
        }
        

        For Beego:

        import "github.com/beego/beego/v2/server/web"
        
        func (ctrl *MainController) handler() {
            ctrl.Ctx.SetCookie("name1", "value1", 200, "/", "example.com", false, false) // Sensitive
        }
        

        For Fiber:

        import "github.com/gofiber/fiber/v2"
        
        func handler(c *fiber.Ctx) error {
            cookie := new(fiber.Cookie)
            cookie.Name = "name"
            cookie.Value = "value"
            c.Cookie(cookie) // Sensitive: HttpOnly is false by default
            return c.SendString("")
        }
        

        For Gin:

        import "github.com/gin-gonic/gin"
        
        func handler(c *gin.Context) {
            c.SetCookie("name", "value", 200, "/", "example.com", false, false) // Sensitive
            c.JSON(http.StatusOK, gin.H{"message": ""})
        }
        

        Compliant Solution

        For Go Standard Library:

        import "net/http"
        
        func handler(w http.ResponseWriter, req *http.Request) {
            cookie := http.Cookie{}
            cookie.Name = "cookiename"
            cookie.Value = "cookievalue"
            cookie.HttpOnly = true
            http.SetCookie(w, &cookie)
        }
        

        For Beego:

        import "github.com/beego/beego/v2/server/web"
        
        func (ctrl *MainController) handler() {
            ctrl.Ctx.SetCookie("name1", "value1", 200, "/", "example.com", false, true)
        }
        

        For Fiber:

        import "github.com/gofiber/fiber/v2"
        
        func handler(c *fiber.Ctx) error {
            cookie := new(fiber.Cookie)
            cookie.Name = "name"
            cookie.Value = "value"
            cookie.HTTPOnly = true
            c.Cookie(cookie)
            return c.SendString("")
        }
        

        For Gin:

        import "github.com/gin-gonic/gin"
        
        func handler(c *gin.Context) {
            c.SetCookie("name", "value", 200, "/", "example.com", false, true)
            c.JSON(http.StatusOK, gin.H{"message": ""})
        }
        

        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 ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use