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
 
Tags
    Impact
      Clean code attribute
        1. Credentials should not be hard-coded

           Vulnerability
        2. Extracting archives should not lead to zip slip vulnerabilities

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

           Vulnerability
        4. Cipher algorithms should be robust

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

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

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

           Vulnerability
        8. Passwords should not be stored in plaintext or with a fast hashing algorithm

           Vulnerability
        9. HTTP request redirections should not be open to forging attacks

           Vulnerability
        10. Logging should not be vulnerable to injection attacks

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

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

           Vulnerability
        13. Cryptographic keys should be robust

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

           Vulnerability
        15. Database queries should not be vulnerable to injection attacks

           Vulnerability
        16. Cipher Block Chaining IVs should be unpredictable

           Vulnerability
        17. XPath expressions should not be vulnerable to injection attacks

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

           Vulnerability
        19. OS commands should not be vulnerable to command injection attacks

           Vulnerability
        20. Password hashing functions should use an unpredictable salt

           Vulnerability

        OS commands should not be vulnerable to command injection attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        OS command injections occur when applications build command lines from untrusted data before executing them with a system shell.
        In that case, an attacker can tamper with the command line construction and force the execution of unexpected commands. This can lead to the compromise of the underlying operating system.

        What is the potential impact?

        An attacker exploiting an OS command injection vulnerability will be able to execute arbitrary commands on the underlying operating system.

        The impact depends on the access control measures taken on the target system OS. In the worst-case scenario, the process runs with root privileges, and therefore any OS commands or programs may be affected.

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

        Denial of service and data leaks

        In this scenario, the attack aims to disrupt the organization’s activities and profit from data leaks.

        An attacker could, for example:

        • download the internal server’s data, most likely to sell it
        • modify data, send malware
        • stop services or exhaust resources (with fork bombs for example)

        This threat is particularly insidious if the attacked organization does not maintain a disaster recovery plan (DRP).

        Root privilege escalation and pivot

        In this scenario, the attacker can do everything described in the previous section. The difference is that the attacker also manages to elevate their privileges to an administrative level and attacks other servers.

        Here, the impact depends on how much the target company focuses on its Defense In Depth. For example, the entire infrastructure can be compromised by a combination of OS injections and misconfiguration of:

        • Docker or Kubernetes clusters
        • cloud services
        • network firewalls and routing
        • OS access control
          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