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

        Using unencrypted databases in mobile applications is security-sensitive

        responsibility - trustworthy
        security
        Security Hotspot

          This rule is deprecated, and will eventually be removed.

          Storing data locally is a common task for mobile applications. Such data includes preferences or authentication tokens for external services, among other things. There are many convenient solutions that allow storing data persistently, for example SQLiteDatabase, SharedPreferences, and Realm. By default these systems store the data unencrypted, thus an attacker with physical access to the device can read them out easily. Access to sensitive data can be harmful for the user of the application, for example when the device gets stolen.

          Ask Yourself Whether

          • The database contains sensitive data that could cause harm when leaked.

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

          Recommended Secure Coding Practices

          It’s recommended to password-encrypt local databases that contain sensitive information. Most systems provide secure alternatives to plain-text storage that should be used. If no secure alternative is available the data can also be encrypted manually before it is stored.

          The encryption password should not be hard-coded in the application. There are different approaches how the password can be provided to encrypt and decrypt the database. In the case of EncryptedSharedPreferences the Android Keystore can be used to store the password. Other databases can rely on EncryptedSharedPreferences to store passwords. The password can also be provided dynamically by the user of the application or it can be fetched from a remote server if the other methods are not feasible.

          Sensitive Code Example

          For SQLiteDatabase:

          SQLiteDatabase db = activity.openOrCreateDatabase("test.db", Context.MODE_PRIVATE, null); // Sensitive
          

          For SharedPreferences:

          SharedPreferences pref = activity.getPreferences(Context.MODE_PRIVATE); // Sensitive
          

          For Realm:

          RealmConfiguration config = new RealmConfiguration.Builder().build();
          Realm realm = Realm.getInstance(config); // Sensitive
          

          Compliant Solution

          Instead of SQLiteDatabase you can use SQLCipher:

          SQLiteDatabase db = SQLiteDatabase.openOrCreateDatabase("test.db", getKey(), null);
          

          Instead of SharedPreferences you can use EncryptedSharedPreferences:

          String masterKeyAlias = new MasterKeys.getOrCreate(MasterKeys.AES256_GCM_SPEC);
          EncryptedSharedPreferences.create(
              "secret",
              masterKeyAlias,
              context,
              EncryptedSharedPreferences.PrefKeyEncryptionScheme.AES256_SIV,
              EncryptedSharedPreferences.PrefValueEncryptionScheme.AES256_GCM
          );
          

          For Realm an encryption key can be specified in the config:

          RealmConfiguration config = new RealmConfiguration.Builder()
              .encryptionKey(getKey())
              .build();
          Realm realm = Realm.getInstance(config);
          

          See

          • OWASP - Top 10 2017 Category A3 - Sensitive Data Exposure
          • OWASP - Top 10 2017 Category A6 - Security Misconfiguration
          • OWASP - Top 10 2021 Category A2 - Cryptographic Failures
          • OWASP - Top 10 2021 Category A4 - Insecure Design
          • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
          • OWASP - Mobile AppSec Verification Standard - Data Storage and Privacy Requirements
          • OWASP - Mobile Top 10 2016 Category M2 - Insecure Data Storage
          • OWASP - Mobile Top 10 2024 Category M9 - Insecure Data Storage
          • CWE - CWE-311 - Missing Encryption of Sensitive Data
            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.2
          • SonarQube ServerAnalyze code in your
            on-premise CI
            Developer Edition
            Available Since
            9.2

          © 2008-2025 SonarSource SA. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use