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: 38 rules found
cwe
    Impact
      Clean code attribute
        1. Credentials should not be hard-coded

           Vulnerability
        2. Hard-coded secrets are security-sensitive

           Security Hotspot
        3. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        4. Extracting archives should not lead to zip slip vulnerabilities

           Vulnerability
        5. JWT should be signed and verified with strong cipher algorithms

           Vulnerability
        6. Cipher algorithms should be robust

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

           Vulnerability
        8. Server hostnames should be verified during SSL/TLS connections

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

           Vulnerability
        10. Using publicly writable directories is security-sensitive

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

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

           Security Hotspot
        13. HTTP request redirections should not be open to forging attacks

           Vulnerability
        14. Logging should not be vulnerable to injection attacks

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

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

           Vulnerability
        17. Using weak hashing algorithms is security-sensitive

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

           Security Hotspot
        19. Cryptographic keys should be robust

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

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

           Security Hotspot
        22. Database queries should not be vulnerable to injection attacks

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

           Security Hotspot
        24. Cipher Block Chaining IVs should be unpredictable

           Vulnerability
        25. Setting loose POSIX file permissions is security-sensitive

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

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

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

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

           Vulnerability
        30. Formatting SQL queries is security-sensitive

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

           Vulnerability
        32. Hard-coded credentials are security-sensitive

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

           Vulnerability
        34. All code should be reachable

           Bug
        35. "switch" statements should have "default" clauses

           Code Smell
        36. Useless "if(true) {...}" and "if(false){...}" blocks should be removed

           Bug
        37. Track uses of "TODO" tags

           Code Smell
        38. Track uses of "FIXME" tags

           Code Smell

        Using publicly writable directories is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        Operating systems have global directories where any user has write access. Those folders are mostly used as temporary storage areas like /tmp in Linux based systems. An application manipulating files from these folders is exposed to race conditions on filenames: a malicious user can try to create a file with a predictable name before the application does. A successful attack can result in other files being accessed, modified, corrupted or deleted. This risk is even higher if the application runs with elevated permissions.

        In the past, it has led to the following vulnerabilities:

        • CVE-2012-2451
        • CVE-2015-1838

        This rule raises an issue whenever it detects a hard-coded path to a publicly writable directory like /tmp (see examples below). It also detects access to environment variables that point to publicly writable directories, e.g., TMP and TMPDIR.

        • /tmp
        • /var/tmp
        • /usr/tmp
        • /dev/shm
        • /dev/mqueue
        • /run/lock
        • /var/run/lock
        • /Library/Caches
        • /Users/Shared
        • /private/tmp
        • /private/var/tmp
        • \Windows\Temp
        • \Temp
        • \TMP

        Ask Yourself Whether

        • Files are read from or written into a publicly writable folder
        • The application creates files with predictable names into a publicly writable folder

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

        Recommended Secure Coding Practices

        • Use a dedicated sub-folder with tightly controlled permissions
        • Use secure-by-design APIs to create temporary files. Such API will make sure:
          • The generated filename is unpredictable
          • The file is readable and writable only by the creating user ID
          • The file descriptor is not inherited by child processes
          • The file will be destroyed as soon as it is closed

        Sensitive Code Example

        Examples of sensitive file creation:

        file, _ = os.Create("/tmp/tempfile.txt") // Sensitive
        
        file, _ = os.Create(os.TempDir()+"/tempfile.txt") // Sensitive
        
        file, _ := os.OpenFile("/tmp/tempfile.txt", os.O_CREATE, 0755) // Sensitive
        
        os.WriteFile("/tmp/tempfile.txt", []byte{"sensitive"}, 0755)  // Sensitive
        

        Example of sensitive directory creation:

        tempdir := "/tmp/tempdir/"
        os.Mkdir(tempdir, 0755)  // Sensitive
        file, _ := os.Create("/tmp/tempdir/tempfile.txt")
        

        Compliant Solution

        Compliant temporary file creation:

        file, _ := os.CreateTemp("", "example-pattern")
        

        Compliant temporary directory creation:

        dir, _ := os.MkdirTemp("", "example-directory")
        filename := filepath.Join(dir, "tempfile.txt")
        file, _ := os.Create(filename)
        

        See

        • OWASP - Top 10 2021 Category A1 - Broken Access Control
        • OWASP - Top 10 2017 Category A5 - Broken Access Control
        • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
        • CWE - CWE-377 - Insecure Temporary File
        • CWE - CWE-379 - Creation of Temporary File in Directory with Incorrect Permissions
        • OWASP, Insecure Temporary File
        • STIG Viewer - Application Security and Development: V-222567 - The application must not be vulnerable to race conditions.
          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