The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.

The attacks and consequences of improperly exporting a component may depend on the exported component:

If access to an exported Activity is not restricted, any application will be able to launch the activity. This may allow a malicious application to gain access to sensitive information, modify the internal state of the application, or trick a user into interacting with the victim application while believing they are still interacting with the malicious application.
If access to an exported Service is not restricted, any application may start and bind to the Service. Depending on the exposed functionality, this may allow a malicious application to perform unauthorized actions, gain access to sensitive information, or corrupt the internal state of the application.
If access to a Content Provider is not restricted to only the expected applications, then malicious applications might be able to access the sensitive data. Note that in Android before 4.2, the Content Provider is automatically exported unless it has been explicitly declared as NOT exported.

Primary

There are three types of components that can be exported in an Android application.

An Activity is an application component that provides a UI for users to interact with. A typical application will have multiple Activity screens that perform different functions, such as a main Activity screen and a separate settings Activity screen.
A Service is an application component that is started by another component to execute an operation in the background, even after the invoking component is terminated. Services do not have a UI component visible to the user.
The Content Provider mechanism can be used to share data with other applications or internally within the same application.

Architecture and Design

Availability
Integrity
Unexpected State
DoS: Crash, Exit, or Restart
DoS: Instability
Varies by Context
Other applications, possibly untrusted, can launch the Activity.

Availability
Integrity
Unexpected State
Gain Privileges or Assume Identity
DoS: Crash, Exit, or Restart
DoS: Instability
Varies by Context
Other applications, possibly untrusted, can bind to the Service.

Confidentiality
Integrity
Read Application Data
Modify Application Data
Other applications, possibly untrusted, can read or modify the data that is offered by the Content Provider.

Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
High

Build and Compilation
Attack Surface Reduction
If they do not need to be shared by other applications, explicitly mark components with android:exported="false" in the application manifest.

Build and Compilation
Attack Surface Reduction
If you only intend to use exported components between related apps under your control, use android:protectionLevel="signature" in the xml manifest to restrict access to applications signed by you.

Build and Compilation
Architecture and Design
Attack Surface Reduction
Limit Content Provider permissions (read/write) as appropriate.

Build and Compilation
Architecture and Design
Separation of Privilege
Limit Content Provider permissions (read/write) as appropriate.

This application is exporting an activity and a service in its manifest.xml:

<activity android:name="com.example.vulnerableApp.mainScreen">

...
<intent-filter><action android:name="com.example.vulnerableApp.OPEN_UI" /><category android:name="android.intent.category.DEFAULT" /></intent-filter>
...

</activity><service android:name="com.example.vulnerableApp.backgroundService">

...
<intent-filter><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.

This application has created a content provider to enable custom search suggestions within the application:

<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.

Allowed
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

CWE Content Team
MITRE
2013-07-02
2.5
2013-07-17

CWE Content Team
MITRE
2014-01-22
Critical
Expanded entry to be more general and include all types of Android components that may be improperly exported.

CWE Content Team
MITRE
2014-02-18
updated Background_Details, Common_Consequences, Demonstrative_Examples, Description, Maintenance_Notes, Name, Potential_Mitigations, References

CWE Content Team
MITRE
2017-11-08
updated References

CWE Content Team
MITRE
2020-02-24
updated Applicable_Platforms, Relationships

CWE Content Team
MITRE
2022-10-13
updated Background_Details

CWE Content Team
MITRE
2023-04-27
updated Detection_Factors, References, Relationships

CWE Content Team
MITRE
2023-06-29
updated Mapping_Notes

CWE Content Team
MITRE
2025-12-11
4.19
2025-12-11
updated Relationships, Weakness_Ordinalities

Improper Restriction of Content Provider Export to Other Applications