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

        Receiving intents is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe
        • android

        Android applications can receive broadcasts from the system or other applications. Receiving intents is security-sensitive. For example, it has led in the past to the following vulnerabilities:

        • CVE-2019-1677
        • CVE-2015-1275

        Receivers can be declared in the manifest or in the code to make them context-specific. If the receiver is declared in the manifest Android will start the application if it is not already running once a matching broadcast is received. The receiver is an entry point into the application.

        Other applications can send potentially malicious broadcasts, so it is important to consider broadcasts as untrusted and to limit the applications that can send broadcasts to the receiver.

        Permissions can be specified to restrict broadcasts to authorized applications. Restrictions can be enforced by both the sender and receiver of a broadcast. If permissions are specified when registering a broadcast receiver, then only broadcasters who were granted this permission can send a message to the receiver.

        This rule raises an issue when a receiver is registered without specifying any broadcast permission.

        Ask Yourself Whether

        • The data extracted from intents is not sanitized.
        • Intents broadcast is not restricted.

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

        Recommended Secure Coding Practices

        Restrict the access to broadcasted intents. See the Android documentation for more information.

        Sensitive Code Example

        import android.content.BroadcastReceiver;
        import android.content.Context;
        import android.content.IntentFilter;
        import android.os.Build;
        import android.os.Handler;
        import android.support.annotation.RequiresApi;
        
        public class MyIntentReceiver {
        
            @RequiresApi(api = Build.VERSION_CODES.O)
            public void register(Context context, BroadcastReceiver receiver,
                                 IntentFilter filter,
                                 String broadcastPermission,
                                 Handler scheduler,
                                 int flags) {
                context.registerReceiver(receiver, filter); // Sensitive
                context.registerReceiver(receiver, filter, flags); // Sensitive
        
                // Broadcasting intent with "null" for broadcastPermission
                context.registerReceiver(receiver, filter, null, scheduler); // Sensitive
                context.registerReceiver(receiver, filter, null, scheduler, flags); // Sensitive
            }
        }
        

        Compliant Solution

        import android.content.BroadcastReceiver;
        import android.content.Context;
        import android.content.IntentFilter;
        import android.os.Build;
        import android.os.Handler;
        import android.support.annotation.RequiresApi;
        
        public class MyIntentReceiver {
        
            @RequiresApi(api = Build.VERSION_CODES.O)
            public void register(Context context, BroadcastReceiver receiver,
                                 IntentFilter filter,
                                 String broadcastPermission,
                                 Handler scheduler,
                                 int flags) {
        
                context.registerReceiver(receiver, filter, broadcastPermission, scheduler);
                context.registerReceiver(receiver, filter, broadcastPermission, scheduler, flags);
            }
        }
        

        See

        • OWASP - Mobile AppSec Verification Standard - Platform Interaction Requirements
        • OWASP - Mobile Top 10 2016 Category M1 - Improper Platform Usage
        • OWASP - Mobile Top 10 2024 Category M3 - Insecure Authentication/Authorization
        • OWASP - Mobile Top 10 2024 Category M4 - Insufficient Input/Output Validation
        • CWE - CWE-925 - Improper Verification of Intent by Broadcast Receiver
        • CWE - CWE-926 - Improper Export of Android Application Components
        • Android documentation - Broadcast Overview - Security considerations and best practices
          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