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

        XPath expressions should not be vulnerable to injection attacks

        intentionality - complete
        security
        Vulnerability
        • cwe
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        XPath injections occur in an application when the application retrieves untrusted data and inserts it into an XML Path (XPath) query without sanitizing it first.

        What is the potential impact?

        In the context of a web application vulnerable to XPath injection:
        After discovering the injection point, attackers insert data into the vulnerable field to execute malicious commands in the affected XML documents.

        The impact of this vulnerability depends on the importance of XML structures in the enterprise.
        In cases where organizations rely on XML structures for business-critical operations or where XML is used only for innocuous data transport, the severity of an attack ranges from critical to harmless.

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

        Data Leaks

        A malicious XPath query allows direct data leakage from one or more databases. Although XML is not as widely used as it once was, this possibility still exists with configuration files, for example.

        Data deletion and denial of service

        The malicious query allows the attacker to delete data in the affected XML documents.
        This threat is particularly insidious if the attacked organization does not maintain a disaster recovery plan (DRP) and if XML structures are considered important, as missing critical data can disrupt the regular operations of an organization.

          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