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
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
 
Tags
    Impact
      Clean code attribute
        1. Sensitive information should not be logged in production builds

           Vulnerability
        2. WebViews should not be vulnerable to cross-app scripting attacks

           Vulnerability
        3. Privileged prompts should not be vulnerable to injection attacks

           Vulnerability
        4. Server-side requests should not be vulnerable to traversing attacks

           Vulnerability
        5. Accessing files should not lead to filesystem oracle attacks

           Vulnerability
        6. Environment variables should not be defined from untrusted input

           Vulnerability
        7. Credentials should not be hard-coded

           Vulnerability
        8. Counter Mode initialization vectors should not be reused

           Vulnerability
        9. XML operations should not be vulnerable to injection attacks

           Vulnerability
        10. JSON operations should not be vulnerable to injection attacks

           Vulnerability
        11. Thread suspensions should not be vulnerable to Denial of Service attacks

           Vulnerability
        12. Components should not be vulnerable to intent redirection

           Vulnerability
        13. XML signatures should be validated securely

           Vulnerability
        14. XML parsers should not be vulnerable to Denial of Service attacks

           Vulnerability
        15. XML parsers should not load external schemas

           Vulnerability
        16. XML parsers should not allow inclusion of arbitrary files

           Vulnerability
        17. Mobile database encryption keys should not be disclosed

           Vulnerability
        18. Applications should not create session cookies from untrusted input

           Vulnerability
        19. Reflection should not be vulnerable to injection attacks

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

           Vulnerability
        21. OS commands should not be vulnerable to argument injection attacks

           Vulnerability
        22. A new session should be created during user authentication

           Vulnerability
        23. Authorizations should be based on strong decisions

           Vulnerability
        24. OpenSAML2 should be configured to prevent authentication bypass

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

           Vulnerability
        26. Cipher algorithms should be robust

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

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

           Vulnerability
        29. Server-side templates should not be vulnerable to injection attacks

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

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

           Vulnerability
        32. Dynamic code execution should not be vulnerable to injection attacks

           Vulnerability
        33. "ActiveMQConnectionFactory" should not be vulnerable to malicious code deserialization

           Vulnerability
        34. NoSQL operations should not be vulnerable to injection attacks

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

           Vulnerability
        36. Logging should not be vulnerable to injection attacks

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

           Vulnerability
        38. Deserialization should not be vulnerable to injection attacks

           Vulnerability
        39. Endpoints should not be vulnerable to reflected cross-site scripting (XSS) attacks

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

           Vulnerability
        41. Persistent entities should not be used as arguments of "@RequestMapping" methods

           Vulnerability
        42. "HttpSecurity" URL patterns should be correctly ordered

           Vulnerability
        43. LDAP connections should be authenticated

           Vulnerability
        44. Cryptographic keys should be robust

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

           Vulnerability
        46. Secure random number generators should not output predictable values

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

           Vulnerability
        48. Cipher Block Chaining IVs should be unpredictable

           Vulnerability
        49. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        50. Classes should not be loaded dynamically

           Vulnerability
        51. Basic authentication should not be used

           Vulnerability
        52. Regular expressions should not be vulnerable to Denial of Service attacks

           Vulnerability
        53. "HttpServletRequest.getRequestedSessionId()" should not be used

           Vulnerability
        54. A secure password should be used when connecting to a database

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

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

           Vulnerability
        57. LDAP queries should not be vulnerable to injection attacks

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

           Vulnerability
        59. Password hashing functions should use an unpredictable salt

           Vulnerability
        60. Exceptions should not be thrown from servlet methods

           Vulnerability

        OpenSAML2 should be configured to prevent authentication bypass

        responsibility - trustworthy
        security
        Vulnerability
        • spring

        The Security Assertion Markup Language (SAML) is a widely used standard in single sign-on systems. In a simplified version, the user authenticates to an Identity Provider which generates a signed SAML Response. This response is then forwarded to a Service Provider for validation and authentication.

        Why is this an issue?

        How can I fix it?

        More Info

        If the Service Provider does not manage to properly validate the incoming SAML response message signatures, attackers might be able to manipulate the response content without the application noticing. Especially, they might be able to alter the authentication-targeted user.

        What is the potential impact?

        By exploiting this vulnerability, an attacker can manipulate the SAML Response to impersonate a different user. This, in turn, can have various consequences on the application’s security.

        Unauthorized Access

        Exploiting this vulnerability allows an attacker with authenticated access to impersonate other users within the SAML-based SSO system. This can lead to unauthorized access to sensitive information, resources, or functionalities the attacker should not have. By masquerading as legitimate users, the attacker can bypass authentication mechanisms and gain unauthorized privileges, potentially compromising the entire system. By impersonating a user with higher privileges, the attacker can gain access to additional resources. Privilege escalation can lead to further compromise of other systems and unauthorized access to critical infrastructure.

        Data Breaches

        With the ability to impersonate other users, an attacker can gain access to sensitive data stored within the SAML-based SSO system. This includes personally identifiable information (PII), financial data, intellectual property, or any other confidential information. Data breaches can result in reputational damage, legal consequences, financial losses, and harm to individuals whose data is exposed.

          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 Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use