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

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

        responsibility - trustworthy
        security
        Vulnerability
        • cwe
        • spring

        The improper storage of passwords poses a significant security risk to software applications. This vulnerability arises when passwords are stored in plaintext or with a fast hashing algorithm. To exploit this vulnerability, an attacker typically requires access to the stored passwords.

        Why is this an issue?

        How can I fix it?

        More Info

        Attackers who would get access to the stored passwords could reuse them without further attacks or with little additional effort.
        Obtaining the plaintext passwords, they could then gain unauthorized access to user accounts, potentially leading to various malicious activities.

        What is the potential impact?

        Plaintext or weakly hashed password storage poses a significant security risk to software applications.

        Unauthorized Access

        When passwords are stored in plaintext or with weak hashing algorithms, an attacker who gains access to the password database can easily retrieve and use the passwords to gain unauthorized access to user accounts. This can lead to various malicious activities, such as unauthorized data access, identity theft, or even financial fraud.

        Credential Reuse

        Many users tend to reuse passwords across multiple platforms. If an attacker obtains plaintext or weakly hashed passwords, they can potentially use these credentials to gain unauthorized access to other accounts held by the same user. This can have far-reaching consequences, as sensitive personal information or critical systems may be compromised.

        Regulatory Compliance

        Many industries and jurisdictions have specific regulations and standards to protect user data and ensure its confidentiality. Storing passwords in plaintext or with weak hashing algorithms can lead to non-compliance with these regulations, potentially resulting in legal consequences, financial penalties, and damage to the reputation of the software application and its developers.

        Recommended practices

        Use secure password hashing algorithms

        In general, you should rely on an algorithm that has no known security vulnerabilities. The MD5 and SHA-1 algorithms should not be used.

        Some algorithms, such as the SHA family functions, are considered strong for some use cases, but are too fast in computation and therefore vulnerable to brute force attacks, especially with bruteforce-attack-oriented hardware.

        To protect passwords, it is therefore important to choose modern, slow password-hashing algorithms. The following algorithms are, in order of strength, the most secure password hashing algorithms to date:

        1. Argon2
        2. scrypt
        3. bcrypt
        4. PBKDF2

        Argon2 should be the best choice, and others should be used when the previous one is not available. For systems that must use FIPS-140-certified algorithms, PBKDF2 should be used.

        Whenever possible, choose the strongest algorithm available. If the algorithm currently used by your system should be upgraded, OWASP documents possible upgrade methods here: Upgrading Legacy Hashes.

          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