CWE-926: Improper Export of Android Application Components

Extended Description

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.

Code Examples & CVEs

Demonstrative Examples

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

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.

BadXML

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

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

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.

BadXML

<provider>android:name="com.example.vulnerableApp.searchDB"android:authorities="com.example.vulnerableApp.searchDB"></provider>

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-926 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-926, Improper Export of Android Application Components, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Attack Surface Reduction controls for Improper Export of Android Application Components

MITRE associates mitigation with Build and Compilation, and Architecture and Design; the listed strategies include Attack Surface Reduction, and Separation of Privilege; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-926 into implementation, review, and verification checks for the affected component.

CWE-926: Improper Export of Android Application Components — MITRE CWE

Triage CWE-926 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-926, Improper Export of Android Application Components, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-926

Apply MITRE's full root-cause mapping guidance when using CWE-926, Improper Export of Android Application Components. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-926 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-926, Improper Export of Android Application Components. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-926: Improper Export of Android Application Components?+

CWE-926: Improper Export of Android Application Components is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Export of Android Application Components?+

If exploited, CWE-926 (Improper Export of Android Application Components) it can compromise Availability, Integrity and Confidentiality, leading to outcomes such as Unexpected State, DoS: Crash, Exit, or Restart, DoS: Instability, Varies by Context, Gain Privileges or Assume Identity and Read Application Data.

How do you prevent or mitigate Improper Export of Android Application Components?+

Recommended mitigations for CWE-926 include: If they do not need to be shared by other applications, explicitly mark components with android:exported="false" in the application manifest. 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. Limit Content Provider permissions (read/write) as appropriate.

Which programming languages are affected by Improper Export of Android Application Components?+

CWE-926 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-926 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-926: Improper Export of Android Application Components

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Strategy

Phase

Description

Strategy

Phase

Description

Strategy

Phase

Description

Strategy

Detection Methods

Code Examples & CVEs

Demonstrative Examples

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-926 with SSDF evidence

Apply Attack Surface Reduction controls for Improper Export of Android Application Components

Triage CWE-926 against known exploitation evidence

Apply precise root-cause mapping to CWE-926

Validate CWE-926 with root-cause mapping checks

Frequently Asked Questions

Learn More