1836
<action android:name="com.example.vulnerableApp.START_BACKGROUND" />
</intent-filter>
...
</service>
Because these components have intent filters but have not explicitly set 'android:exported=false'
elsewhere in the manifest, they are automatically exported so that any other application can launch
them. This may lead to unintended behavior or exploits.
Example 2:
This application has created a content provider to enable custom search suggestions within the
application:
Example Language: XML (Bad)
<provider>
android:name="com.example.vulnerableApp.searchDB"
android:authorities="com.example.vulnerableApp.searchDB">
</provider>
Because this content provider is only intended to be used within the application, it does not need to
be exported. However, in Android before 4.2, it is automatically exported thus potentially allowing
malicious applications to access sensitive information.
MemberOf Relationships
This MemberOf relationships table shows additional CWE Catgeories and Views that reference this
weakness as a member. This information is often useful in understanding where a weakness fits
within the context of external information sources.
Nature Type ID Name Page
MemberOf 1396 Comprehensive Categorization: Access Control 1400 2519
References
[REF-923]Android Open Source Project. "Security Tips". 2013 July 6. < https://
developer.android.com/training/articles/security-tips#ContentProviders >.2023-04-07.
CWE-927: Use of Implicit Intent for Sensitive Communication
Weakness ID : 927
Structure : Simple
Abstraction : Variant
Description
The Android application uses an implicit intent for transmitting sensitive data to other applications.
Extended Description
Since an implicit intent does not specify a particular application to receive the data, any application
can process the intent by using an Intent Filter for that intent. This can allow untrusted applications
to obtain sensitive data. There are two variations on the standard broadcast intent, ordered and
sticky.
Ordered broadcast intents are delivered to a series of registered receivers in order of priority as
declared by the Receivers. A malicious receiver can give itself a high priority and cause a denial
of service by stopping the broadcast from propagating further down the chain. There is also the
possibility of malicious data modification, as a receiver may also alter the data within the Intent
before passing it on to the next receiver. The downstream components have no way of asserting
that the data has not been altered earlier in the chain.
CWE Version 4.14
CWE-927: Use of Implicit Intent for Sensitive Communication
CWE-927: Use of Implicit Intent for Sensitive Communication