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

        HTTP request redirections should not be open to forging attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Open redirection occurs when an application uses user-controllable data to redirect users to a URL.

        An attacker with malicious intent could manipulate a user to browse into a specially crafted URL, such as https://trusted.example.com?url=evil.example.com, to redirect the victim to his evil domain.

        Tricking users into sending the malicious HTTP request is usually the main task of exploiting an open redirection. Often, it requires an attacker to build a credible pretext to prevent suspicions from the victim.

        Attackers commonly use open redirect exploits in mass phishing campaigns.

        What is the potential impact?

        If an attacker tricks a user into opening a link of his choice, the user is redirected to a domain controlled by the attacker.

        From then on, the attacker can perform various malicious actions, some more impactful than others.

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

        Domain Mirroring

        A malicious link redirects to an attacker’s controlled website mirroring the interface of a web application trusted by the user. Due to the similarity in the application appearance and the apparently trustable clicked hyperlink, the user struggles to identify that they are browsing on a malicious domain.

        Depending on the attacker’s purpose, the malicious website can leak credentials, bypass Multi-Factor Authentication (MFA), and reach any authenticated data or action.

        Malware Distribution

        A malicious link redirects to an attacker’s controlled website that serves malware. On the same basis as the domain mirroring exploitation, the attacker develops a spearphishing or phishing campaign with a carefully crafted pretext that would result in the download and potential execution of a hosted malicious file.
        The worst-case scenario could result in complete system compromise.

          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