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: 23 rules found
symbolic-execution
    Impact
      Clean code attribute
        1. XML signatures should be validated securely

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

           Vulnerability
        3. XML parsers should not load external schemas

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

           Vulnerability
        5. Nullness of parameters should be guaranteed

           Code Smell
        6. Assignments should not be redundant

           Code Smell
        7. Consumed Stream pipelines should not be reused

           Bug
        8. Intermediate Stream methods should not be left unused

           Bug
        9. "Map.get" and value test should be replaced with single method call

           Code Smell
        10. Optional value should only be accessed after calling isPresent()

           Bug
        11. Custom resources should be closed

           Bug
        12. Zero should not be a possible denominator

           Bug
        13. Methods returns should not be invariant

           Code Smell
        14. Min and max used in combination should not always return the same value

           Bug
        15. XML parsers should not be vulnerable to XXE attacks

           Vulnerability
        16. Files opened in append mode should not be used with "ObjectOutputStream"

           Bug
        17. "@NonNull" values should not be set to null

           Bug
        18. Boolean expressions should not be gratuitous

           Code Smell
        19. Conditionally executed code should be reachable

           Bug
        20. Null pointers should not be dereferenced

           Bug
        21. Locks should be released on all paths

           Bug
        22. Loops should not be infinite

           Bug
        23. Resources should be closed

           Bug

        Resources should be closed

        intentionality - complete
        reliability
        Bug
        • cwe
        • leak
        • denial-of-service
        • cert
        • symbolic-execution

        Why is this an issue?

        More Info

        Connections, streams, files, and other classes that implement the Closeable interface or its super-interface, AutoCloseable, needs to be closed after use. Further, that close call must be made in a finally block otherwise an exception could keep the call from being made. Preferably, when class implements AutoCloseable, resource should be created using "try-with-resources" pattern and will be closed automatically.

        Failure to properly close resources will result in a resource leak which could bring first the application and then perhaps the box the application is on to their knees.

        Noncompliant code example

        private void readTheFile() throws IOException {
          Path path = Paths.get(this.fileName);
          BufferedReader reader = Files.newBufferedReader(path, this.charset);
          // ...
          reader.close();  // Noncompliant
          // ...
          Files.lines("input.txt").forEach(System.out::println); // Noncompliant: The stream needs to be closed
        }
        
        private void doSomething() {
          OutputStream stream = null;
          try {
            for (String property : propertyList) {
              stream = new FileOutputStream("myfile.txt");  // Noncompliant
              // ...
            }
          } catch (Exception e) {
            // ...
          } finally {
            stream.close();  // Multiple streams were opened. Only the last is closed.
          }
        }
        

        Compliant solution

        private void readTheFile(String fileName) throws IOException {
            Path path = Paths.get(fileName);
            try (BufferedReader reader = Files.newBufferedReader(path, StandardCharsets.UTF_8)) {
              reader.readLine();
              // ...
            }
            // ..
            try (Stream<String> input = Files.lines("input.txt"))  {
              input.forEach(System.out::println);
            }
        }
        
        private void doSomething() {
          OutputStream stream = null;
          try {
            stream = new FileOutputStream("myfile.txt");
            for (String property : propertyList) {
              // ...
            }
          } catch (Exception e) {
            // ...
          } finally {
            stream.close();
          }
        }
        

        Exceptions

        Instances of the following classes are ignored by this rule because close has no effect:

        • java.io.ByteArrayOutputStream
        • java.io.ByteArrayInputStream
        • java.io.CharArrayReader
        • java.io.CharArrayWriter
        • java.io.StringReader
        • java.io.StringWriter

        Java 7 introduced the try-with-resources statement, which implicitly closes Closeables. All resources opened in a try-with-resources statement are ignored by this rule.

        try (BufferedReader br = new BufferedReader(new FileReader(fileName))) {
          //...
        }
        catch ( ... ) {
          //...
        }
        
          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