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: 20 rules found
bad-practice
    Impact
      Clean code attribute
        1. Similar tests should be grouped in a single Parameterized test

           Code Smell
        2. An iteration on a Collection should be performed on the type handled by the Collection

           Code Smell
        3. "enum" fields should not be publicly mutable

           Code Smell
        4. "Thread.sleep" should not be used in tests

           Code Smell
        5. Formatting SQL queries is security-sensitive

           Security Hotspot
        6. Loops with at most one iteration should be refactored

           Bug
        7. JUnit4 @Ignored and JUnit5 @Disabled annotations should be used to disable tests and should provide a rationale

           Code Smell
        8. Declarations should use Java collection interfaces such as "List" rather than specific implementation classes such as "LinkedList"

           Code Smell
        9. Track uses of "CHECKSTYLE:OFF" suppression comments

           Code Smell
        10. Track uses of "NOPMD" suppression comments

           Code Smell
        11. "switch" statements should have at least 3 "case" clauses

           Code Smell
        12. Track uses of "NOSONAR" comments

           Code Smell
        13. Execution of the Garbage Collector should be triggered only by the JVM

           Code Smell
        14. Interfaces should not solely consist of constants

           Code Smell
        15. Nested code blocks should not be used

           Code Smell
        16. Throwable and Error should not be caught

           Code Smell
        17. "@Override" should be used on overriding and implementing methods

           Code Smell
        18. Strings literals should be placed on the left side when checking for equality

           Code Smell
        19. Deprecated elements should have both the annotation and the Javadoc tag

           Code Smell
        20. Standard outputs should not be used directly to log anything

           Code Smell

        Formatting SQL queries is security-sensitive

        intentionality - complete
        maintainability
        security
        Security Hotspot
        • cwe
        • spring
        • bad-practice
        • cert
        • hibernate
        • sql

        Formatted SQL queries can be difficult to maintain, debug and can increase the risk of SQL injection when concatenating untrusted values into the query. However, this rule doesn’t detect SQL injections (unlike rule S3649), the goal is only to highlight complex/formatted queries.

        Ask Yourself Whether

        • Some parts of the query come from untrusted values (like user inputs).
        • The query is repeated/duplicated in other parts of the code.
        • The application must support different types of relational databases.

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • Use parameterized queries, prepared statements, or stored procedures and bind variables to SQL query parameters.
        • Consider using ORM frameworks if there is a need to have an abstract layer to access data.

        Sensitive Code Example

        public User getUser(Connection con, String user) throws SQLException {
        
          Statement stmt1 = null;
          Statement stmt2 = null;
          PreparedStatement pstmt;
          try {
            stmt1 = con.createStatement();
            ResultSet rs1 = stmt1.executeQuery("GETDATE()"); // No issue; hardcoded query
        
            stmt2 = con.createStatement();
            ResultSet rs2 = stmt2.executeQuery("select FNAME, LNAME, SSN " +
                         "from USERS where UNAME=" + user);  // Sensitive
        
            pstmt = con.prepareStatement("select FNAME, LNAME, SSN " +
                         "from USERS where UNAME=" + user);  // Sensitive
            ResultSet rs3 = pstmt.executeQuery();
        
            //...
        }
        
        public User getUserHibernate(org.hibernate.Session session, String data) {
        
          org.hibernate.Query query = session.createQuery(
                    "FROM students where fname = " + data);  // Sensitive
          // ...
        }
        

        Compliant Solution

        public User getUser(Connection con, String user) throws SQLException {
        
          Statement stmt1 = null;
          PreparedStatement pstmt = null;
          String query = "select FNAME, LNAME, SSN " +
                         "from USERS where UNAME=?"
          try {
            stmt1 = con.createStatement();
            ResultSet rs1 = stmt1.executeQuery("GETDATE()");
        
            pstmt = con.prepareStatement(query);
            pstmt.setString(1, user);  // Good; PreparedStatements escape their inputs.
            ResultSet rs2 = pstmt.executeQuery();
        
            //...
          }
        }
        
        public User getUserHibernate(org.hibernate.Session session, String data) {
        
          org.hibernate.Query query =  session.createQuery("FROM students where fname = ?");
          query = query.setParameter(0,data);  // Good; Parameter binding escapes all input
        
          org.hibernate.Query query2 =  session.createQuery("FROM students where fname = " + data); // Sensitive
          // ...
        

        See

        • OWASP - Top 10 2021 Category A3 - Injection
        • OWASP - Top 10 2017 Category A1 - Injection
        • CWE - CWE-89 - Improper Neutralization of Special Elements used in an SQL Command
        • CWE - CWE-564 - SQL Injection: Hibernate
        • CWE - CWE-20 - Improper Input Validation
        • CWE - CWE-943 - Improper Neutralization of Special Elements in Data Query Logic
        • CERT, IDS00-J. - Prevent SQL injection
        • Derived from FindSecBugs rules Potential SQL/JPQL Injection (JPA), Potential SQL/JDOQL Injection (JDO), Potential SQL/HQL Injection (Hibernate)
          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