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

        Database queries should not be vulnerable to injection attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • sql
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Database injections (such as SQL injections) occur in an application when the application retrieves data from a user or a third-party service and inserts it into a database query without sanitizing it first.

        If an application contains a database query that is vulnerable to injections, it is exposed to attacks that target any database where that query is used.

        A user with malicious intent is able to modify the existing query to change its logic to a malicious one.

        After creating the malicious request, the attacker can attack the databases affected by this vulnerability without relying on any pre-requisites.

        What is the potential impact?

        In the context of a web application that is vulnerable to SQL injection:
        After discovering the injection, attackers inject data into the vulnerable field to execute malicious commands in the affected databases.

        Below are some real-world scenarios that illustrate some impacts of an attacker exploiting the vulnerability.

        Identity spoofing and data manipulation

        A malicious database query enables privilege escalation or direct data leakage from one or more databases. This threat is the most widespread impact.

        Data deletion and denial of service

        The malicious query makes it possible for the attacker to delete data in the affected databases.
        This threat is particularly insidious if the attacked organization does not maintain a disaster recovery plan (DRP).

        Chaining DB injections with other vulnerabilities

        Attackers who exploit SQL injections rely on other vulnerabilities to maximize their profits.
        Most of the time, organizations overlook some defense in depth measures because they assume attackers cannot reach certain points in the infrastructure. This misbehavior can lead to multiple attacks with great impact:

        • When secrets are stored unencrypted in databases: Secrets can be exfiltrated and lead to compromise of other components.
        • If server-side OS and/or database permissions are misconfigured, injection can lead to remote code execution (RCE).
          • See our article on this topic
          Available In:
        • 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