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
Filtered: 106 rules found
Tags
    security
      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. Processing persistent unique identifiers is security-sensitive

           Security Hotspot
        5. Exposing native code through JavaScript interfaces is security-sensitive

           Security Hotspot
        6. Methods annotated with "@BeforeTransaction" or "@AfterTransaction" must respect the contract

           Code Smell
        7. Methods returning "Page" or "Slice" must take "Pageable" as an input parameter

           Code Smell
        8. "@Scheduled" annotation should only be applied to no-arg methods

           Bug
        9. @InitBinder methods should have void return type

           Code Smell
        10. "@Cache*" annotations should only be applied on concrete classes

           Code Smell
        11. Injecting data into static fields is not supported by Spring

           Code Smell
        12. Server-side requests should not be vulnerable to traversing attacks

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

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

           Vulnerability
        15. Credentials should not be hard-coded

           Vulnerability
        16. Counter Mode initialization vectors should not be reused

           Vulnerability
        17. Hard-coded secrets are security-sensitive

           Security Hotspot
        18. XML operations should not be vulnerable to injection attacks

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

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

           Vulnerability
        21. Components should not be vulnerable to intent redirection

           Vulnerability
        22. XML signatures should be validated securely

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

           Vulnerability
        24. XML parsers should not load external schemas

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

           Vulnerability
        26. Enabling file access for WebViews is security-sensitive

           Security Hotspot
        27. Enabling JavaScript support for WebViews is security-sensitive

           Security Hotspot
        28. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        29. Mobile database encryption keys should not be disclosed

           Vulnerability
        30. Using unencrypted files in mobile applications is security-sensitive

           Security Hotspot
        31. Using biometric authentication without a cryptographic solution is security-sensitive

           Security Hotspot
        32. Using unencrypted databases in mobile applications is security-sensitive

           Security Hotspot
        33. Authorizing non-authenticated users to use keys in the Android KeyStore is security-sensitive

           Security Hotspot
        34. Applications should not create session cookies from untrusted input

           Vulnerability
        35. Using long-term access keys is security-sensitive

           Security Hotspot
        36. Reflection should not be vulnerable to injection attacks

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

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

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

           Vulnerability
        40. Using slow regular expressions is security-sensitive

           Security Hotspot
        41. Authorizations should be based on strong decisions

           Vulnerability
        42. Allowing user enumeration is security-sensitive

           Security Hotspot
        43. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        44. Disclosing fingerprints from web application technologies is security-sensitive

           Security Hotspot
        45. OpenSAML2 should be configured to prevent authentication bypass

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

           Vulnerability
        47. Cipher algorithms should be robust

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

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

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

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

           Vulnerability
        52. Using publicly writable directories is security-sensitive

           Security Hotspot
        53. Passwords should not be stored in plaintext or with a fast hashing algorithm

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

           Vulnerability
        55. Using clear-text protocols is security-sensitive

           Security Hotspot
        56. Accessing Android external storage is security-sensitive

           Security Hotspot
        57. Receiving intents is security-sensitive

           Security Hotspot
        58. Broadcasting intents is security-sensitive

           Security Hotspot
        59. "ActiveMQConnectionFactory" should not be vulnerable to malicious code deserialization

           Vulnerability
        60. Disabling auto-escaping in template engines is security-sensitive

           Security Hotspot
        61. NoSQL operations should not be vulnerable to injection attacks

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

           Vulnerability
        63. Logging should not be vulnerable to injection attacks

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

           Vulnerability
        65. Deserialization should not be vulnerable to injection attacks

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

           Vulnerability
        67. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        68. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        69. Server certificates should be verified during SSL/TLS connections

           Vulnerability
        70. Configuring loggers is security-sensitive

           Security Hotspot
        71. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        72. Persistent entities should not be used as arguments of "@RequestMapping" methods

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

           Vulnerability
        74. Using unsafe Jackson deserialization configuration is security-sensitive

           Security Hotspot
        75. Setting JavaBean properties is security-sensitive

           Security Hotspot
        76. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        77. Disabling CSRF protections is security-sensitive

           Security Hotspot
        78. Allowing deserialization of LDAP objects is security-sensitive

           Security Hotspot
        79. LDAP connections should be authenticated

           Vulnerability
        80. Cryptographic keys should be robust

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

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

           Vulnerability
        83. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        84. Allowing both safe and unsafe HTTP methods is security-sensitive

           Security Hotspot
        85. Database queries should not be vulnerable to injection attacks

           Vulnerability
        86. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        87. Cipher Block Chaining IVs should be unpredictable

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

           Vulnerability
        89. Classes should not be loaded dynamically

           Vulnerability
        90. Basic authentication should not be used

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

           Vulnerability
        92. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        93. Using non-standard cryptographic algorithms is security-sensitive

           Security Hotspot
        94. "HttpServletRequest.getRequestedSessionId()" should not be used

           Vulnerability
        95. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        96. A secure password should be used when connecting to a database

           Vulnerability
        97. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        98. XPath expressions should not be vulnerable to injection attacks

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

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

           Vulnerability
        101. Formatting SQL queries is security-sensitive

           Security Hotspot
        102. OS commands should not be vulnerable to command injection attacks

           Vulnerability
        103. Hard-coded passwords are security-sensitive

           Security Hotspot
        104. Password hashing functions should use an unpredictable salt

           Vulnerability
        105. Exceptions should not be thrown from servlet methods

           Vulnerability
        106. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Regular expressions should not be vulnerable to Denial of Service attacks

        intentionality - efficient
        security
        Vulnerability
        • cwe
        • denial-of-service
        • injection

        Why is this an issue?

        How can I fix it?

        More Info

        Regular expression injections occur when the application retrieves untrusted data and uses it as a regex to pattern match a string with it.

        Most regular expression search engines use backtracking to try all possible regex execution paths when evaluating an input. Sometimes this can lead to performance problems also referred to as catastrophic backtracking situations.

        What is the potential impact?

        In the context of a web application vulnerable to regex injection:
        After discovering the injection point, attackers insert data into the vulnerable field to make the affected component inaccessible.

        Depending on the application’s software architecture and the injection point’s location, the impact may or may not be visible.

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

        Self Denial of Service

        In cases where the complexity of the regular expression is exponential to the input size, a small, carefully-crafted input (for example, 20 chars) can trigger catastrophic backtracking and cause a denial of service of the application.

        Super-linear regex complexity can produce the same effects for a large, carefully crafted input (thousands of chars).

        If the component jeopardized by this vulnerability is not a bottleneck that acts as a single point of failure (SPOF) within the application, the denial of service might only affect the attacker who initiated it.

        Such benign denial of service can also occur in architectures that rely heavily on containers and container orchestrators. Replication systems would detect the failure of a container and automatically replace it.

        Infrastructure SPOFs

        However, a denial of service attack can be critical to the enterprise if it targets a SPOF component. Sometimes the SPOF is a software architecture vulnerability (such as a single component on which multiple critical components depend) or an operational vulnerability (for example, insufficient container creation capabilities or failures from containers to terminate).

        In either case, attackers aim to exploit the infrastructure weakness by sending as many malicious payloads as possible, using potentially huge offensive infrastructures.

        These threats are particularly insidious if the attacked organization does not maintain a disaster recovery plan (DRP).

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • 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