CWE-926: Improper Export of Android Application Components
Description
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.
- Abstraction
- VariantA weakness tied to a specific language, technology or resource.
- Likelihood of exploit
- Not rated by MITRE
- Status
- Incomplete
Common consequences
- AvailabilityIntegrity
Unexpected State; DoS: Crash, Exit, or Restart; DoS: Instability; Varies by Context
Other applications, possibly untrusted, can launch the Activity.
- AvailabilityIntegrity
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.
- ConfidentialityIntegrity
Read Application Data; Modify Application Data
Other applications, possibly untrusted, can read or modify the data that is offered by the Content Provider.
Potential mitigations
- Build and CompilationAttack 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 CompilationAttack 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 CompilationArchitecture and DesignAttack Surface Reduction
Limit Content Provider permissions (read/write) as appropriate.
- Build and CompilationArchitecture and DesignSeparation of Privilege
Limit Content Provider permissions (read/write) as appropriate.
Related weaknesses
Parent weaknesses
CAPEC attack patterns that exploit it
CWE 4.20 links no CAPEC attack pattern to this weakness.