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. Processing persistent unique identifiers is security-sensitive

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

           Security Hotspot
        3. Hard-coded secrets are security-sensitive

           Security Hotspot
        4. Enabling file access for WebViews is security-sensitive

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

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

           Security Hotspot
        7. Using unencrypted files in mobile applications is security-sensitive

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

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

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

           Security Hotspot
        11. Using long-term access keys is security-sensitive

           Security Hotspot
        12. Using slow regular expressions is security-sensitive

           Security Hotspot
        13. Allowing user enumeration is security-sensitive

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

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

           Security Hotspot
        16. Using publicly writable directories is security-sensitive

           Security Hotspot
        17. Using clear-text protocols is security-sensitive

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

           Security Hotspot
        19. Receiving intents is security-sensitive

           Security Hotspot
        20. Broadcasting intents is security-sensitive

           Security Hotspot
        21. Disabling auto-escaping in template engines is security-sensitive

           Security Hotspot
        22. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

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

           Security Hotspot
        24. Configuring loggers is security-sensitive

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

           Security Hotspot
        26. Using unsafe Jackson deserialization configuration is security-sensitive

           Security Hotspot
        27. Setting JavaBean properties is security-sensitive

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

           Security Hotspot
        29. Disabling CSRF protections is security-sensitive

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

           Security Hotspot
        31. Searching OS commands in PATH is security-sensitive

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

           Security Hotspot
        33. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        34. Setting loose POSIX file permissions is security-sensitive

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

           Security Hotspot
        36. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        37. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        38. Formatting SQL queries is security-sensitive

           Security Hotspot
        39. Hard-coded passwords are security-sensitive

           Security Hotspot
        40. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Disclosing fingerprints from web application technologies is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        Disclosure of version information, usually overlooked by developers but disclosed by default by the systems and frameworks in use, can pose a significant security risk depending on the production environment.

        Once this information is public, attackers can use it to identify potential security holes or vulnerabilities specific to that version.

        Furthermore, if the published version information indicates the use of outdated or unsupported software, it becomes easier for attackers to exploit known vulnerabilities. They can search for published vulnerabilities related to that version and launch attacks that specifically target those vulnerabilities.

        Ask Yourself Whether

        • Version information is accessible to end users.
        • Internal systems do not benefit from timely patch management workflows.

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

        Recommended Secure Coding Practices

        In general, it is recommended to keep internal technical information within internal systems to control what attackers know about the underlying architectures. This is known as the "need to know" principle.

        The most effective solution is to remove version information disclosure from what end users can see, such as the "x-powered-by" header.
        This can be achieved directly through the web application code, server (nginx, apache) or firewalls.

        Disabling the server signature provides additional protection by reducing the amount of information available to attackers. Note, however, that this does not provide as much protection as regular updates and patches.
        Security by obscurity is the least foolproof solution of all. It should never be the only defense mechanism and should always be combined with other security measures.

        Sensitive Code Example

        @GetMapping(value = "/example")
        public ResponseEntity<String> example() {
          HttpHeaders responseHeaders = new HttpHeaders();
          responseHeaders.set("x-powered-by", "myproduct"); // Sensitive
        
          return new ResponseEntity<String>(
              "example",
              responseHeaders,
              HttpStatus.CREATED);
        }
        

        Compliant Solution

        Do not disclose version information unless necessary. The x-powered-by or Server HTTP headers should not be used.

        See

        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP Testing Guide - OTG-INFO-008 - Fingerprint Web Application Framework
        • OWASP - Top 10 2017 Category A6 - Security Misconfiguration
        • CWE - CWE-200 - Information Exposure
          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