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
android
    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. Bluetooth should be configured to use low power

           Code Smell
        4. Motion Sensor should not use gyroscope

           Code Smell
        5. Use Fused Location to optimize battery power

           Code Smell
        6. High frame rates should not be used

           Code Smell
        7. Exact alarms should not be abused

           Code Smell
        8. Proper Sensor Resource Management

           Code Smell
        9. Components should not be vulnerable to intent redirection

           Vulnerability
        10. Enabling file access for WebViews is security-sensitive

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

           Security Hotspot
        12. Mobile database encryption keys should not be disclosed

           Vulnerability
        13. Using biometric authentication without a cryptographic solution is security-sensitive

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

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

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

           Security Hotspot
        17. Receiving intents is security-sensitive

           Security Hotspot
        18. Broadcasting intents is security-sensitive

           Security Hotspot
        19. Database queries should not be vulnerable to injection attacks

           Vulnerability
        20. URIs should not be hardcoded

           Code Smell

        Authorizing non-authenticated users to use keys in the Android KeyStore is security-sensitive

        consistency - conventional
        security
        Security Hotspot
        • cwe
        • android

        Android KeyStore is a secure container for storing key materials, in particular it prevents key materials extraction, i.e. when the application process is compromised, the attacker cannot extract keys but may still be able to use them. It’s possible to enable an Android security feature, user authentication, to restrict usage of keys to only authenticated users. The lock screen has to be unlocked with defined credentials (pattern/PIN/password, biometric).

        Ask Yourself Whether

        • The application requires prohibiting the use of keys in case of compromise of the application process.
        • The key material is used in the context of a highly sensitive application like a e-banking mobile app.

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

        Recommended Secure Coding Practices

        It’s recommended to enable user authentication (by setting setUserAuthenticationRequired to true during key generation) to use keys for a limited duration of time (by setting appropriate values to setUserAuthenticationValidityDurationSeconds), after which the user must re-authenticate.

        Sensitive Code Example

        Any user can use the key:

        KeyGenerator keyGenerator = KeyGenerator.getInstance(KeyProperties.KEY_ALGORITHM_AES, "AndroidKeyStore");
        
        KeyGenParameterSpec builder = new KeyGenParameterSpec.Builder("test_secret_key_noncompliant", KeyProperties.PURPOSE_ENCRYPT | KeyProperties.PURPOSE_DECRYPT) // Noncompliant
            .setBlockModes(KeyProperties.BLOCK_MODE_GCM)
            .setEncryptionPaddings(KeyProperties.ENCRYPTION_PADDING_NONE)
            .build();
        
        keyGenerator.init(builder);
        

        Compliant Solution

        The use of the key is limited to authenticated users (for a duration of time defined to 60 seconds):

        KeyGenerator keyGenerator = KeyGenerator.getInstance(KeyProperties.KEY_ALGORITHM_AES, "AndroidKeyStore");
        
        KeyGenParameterSpec builder = new KeyGenParameterSpec.Builder("test_secret_key", KeyProperties.PURPOSE_ENCRYPT | KeyProperties.PURPOSE_DECRYPT)
            .setBlockModes(KeyProperties.BLOCK_MODE_GCM)
            .setEncryptionPaddings(KeyProperties.ENCRYPTION_PADDING_NONE)
            .setUserAuthenticationRequired(true)
            .setUserAuthenticationParameters (60, KeyProperties.AUTH_DEVICE_CREDENTIAL)
            .build();
        
        keyGenerator.init(builder)
        

        See

        • OWASP - Top 10 2021 Category A4 - Insecure Design
        • OWASP - Mobile AppSec Verification Standard - Authentication and Session Management Requirements
        • OWASP - Mobile Top 10 2016 Category M4 - Insecure Authentication
        • OWASP - Mobile Top 10 2024 Category M3 - Insecure Authentication/Authorization
        • OWASP - Mobile Top 10 2024 Category M10 - Insufficient Cryptography
        • CWE - CWE-522 - Insufficiently Protected Credentials
        • developer.android.com - Android keystore system
        • developer.android.com - Require user authentication for key use
          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