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: 28 rules found
error-handling
    Impact
      Clean code attribute
        1. Return values should not be ignored when they contain the operation status code

           Bug
        2. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        3. "java.nio.Files#delete" should be preferred

           Code Smell
        4. Exceptions should not be created without being thrown

           Bug
        5. Unit tests should throw exceptions

           Code Smell
        6. "catch" clauses should do more than rethrow

           Code Smell
        7. "Iterator.next()" methods should throw "NoSuchElementException"

           Bug
        8. "IllegalMonitorStateException" should not be caught

           Code Smell
        9. "Exception" should not be caught when not required by called methods

           Code Smell
        10. Classes named like "Exception" should extend "Exception" or a subclass

           Code Smell
        11. "InterruptedException" and "ThreadDeath" should not be ignored

           Bug
        12. Exceptions should be either logged or rethrown but not both

           Code Smell
        13. "main" should not "throw" anything

           Code Smell
        14. Exceptions should not be thrown from servlet methods

           Vulnerability
        15. "NullPointerException" should not be caught

           Code Smell
        16. "NullPointerException" should not be explicitly thrown

           Code Smell
        17. "java.lang.Error" should not be extended

           Code Smell
        18. Exception types should not be tested using "instanceof" in catch blocks

           Code Smell
        19. Throwable and Error should not be caught

           Code Smell
        20. Exception handlers should preserve the original exceptions

           Code Smell
        21. Exception classes should have final fields

           Code Smell
        22. Exceptions should not be thrown in finally blocks

           Code Smell
        23. Checked exceptions should not be thrown

           Code Smell
        24. Public methods should throw at most one checked exception

           Code Smell
        25. Jump statements should not occur in "finally" blocks

           Bug
        26. Try-catch blocks should not be nested

           Code Smell
        27. Exceptions in "throws" clauses should not be superfluous

           Code Smell
        28. Generic exceptions should never be thrown

           Code Smell

        Exceptions should not be thrown from servlet methods

        consistency - conventional
        security
        Vulnerability
        • cwe
        • error-handling
        • cert

        Why is this an issue?

        How can I fix it?

        More Info

        Servlets are components in Java web development, responsible for processing HTTP requests and generating responses. In this context, exceptions are used to handle and manage unexpected errors or exceptional conditions that may occur during the execution of a servlet.

        Catching exceptions within the servlet allows us to convert them into meaningful, user-friendly messages. Otherwise, failing to catch exceptions will propagate them to the servlet container, where the default error-handling mechanism may impact the overall security and stability of the server.

        Possible security problems are:

        1. Vulnerability to denial-of-service attacks: Not caught exceptions can leave the servlet container in an unstable state, which can exhaust the available resources and make the system unavailable in the worst cases.
        2. Exposure of sensitive information: Exceptions handled by the servlet container, by default, expose detailed error messages or debugging information to the user, which may contain sensitive data such as stack traces, database connection, or system configuration.

        Unfortunately, servlet method signatures do not force developers to handle IOException and ServletException:

        public void doGet(HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException {
        }
        

        To prevent this risk, this rule enforces all exceptions to be caught within the "do*" methods of servlet classes.

          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