CWE-926 Variant Incomplete

Improper Export of Android Application Components

This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps without enforcing proper security checks. This allows…

Definition

What is CWE-926?

This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps without enforcing proper security checks. This allows unintended or malicious applications to interact with the component, potentially leading to data theft, unauthorized actions, or application compromise.

When you export an Android component without restrictions, you create an open door for other apps on the device. For Activities, this can let malicious apps launch your screens to steal data, modify your app's state, or impersonate your UI to trick users. For Services, unauthorized apps can bind to and trigger functionality, potentially performing actions they shouldn't or corrupting your app's logic. Content Providers are especially risky, as versions of Android before 4.2 automatically export them unless you explicitly set them as private, which can lead to direct data leaks. To prevent this, always explicitly set the `android:exported` attribute in your AndroidManifest.xml and implement strong permission checks. Use signature-level permissions for components that should only communicate with your own apps. For Content Providers, explicitly declare them as not exported if they're for internal use only, and always apply URI permissions for temporary data sharing. Never rely on default export behaviors, as they often prioritize convenience over security.

Auswirkungen in der Praxis

Real-world CVEs caused by CWE-926

Bisher sind in MITREs Katalog keine öffentlichen CVE-Referenzen mit dieser CWE verknüpft.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

1
This application is exporting an activity and a service in its manifest.xml:
2
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.
3
This application has created a content provider to enable custom search suggestions within the application:
4
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.

Verwundbares Codebeispiel

Vulnerable XML

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

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

Sicheres Codebeispiel

Secure pseudo

Sicher pseudo

// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Präventions-Checkliste

How to prevent CWE-926

Build and Compilation 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 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 Limit Content Provider permissions (read/write) as appropriate.
Build and Compilation / Architecture and Design Limit Content Provider permissions (read/write) as appropriate.

Erkennungssignale

How to detect CWE-926

Automated Static Analysis High

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

CWE-926

Don't catalog this weakness. Prove it's reachable.

Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.

Request AI Swarm Pentest

Häufig gestellte Fragen

Frequently asked questions

Was ist CWE-926?

Wie gravierend ist CWE-926?

MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.

Welche Sprachen oder Plattformen sind von CWE-926 betroffen?

MITRE lists the following affected platforms: Mobile.

Wie kann ich CWE-926 verhindern?

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.

Wie erkennt und behebt Plexicus CWE-926?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-926 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-926?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/926.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Verwandte Schwachstellen

Weaknesses related to CWE-926

CWE-285 Parent

Bereit zu validieren, was zählt.

Plexicus ist Proof-Driven AppSec: validierte Funde, kontextuelles Verständnis und geprüfte Remediation — in Evidenz verankert, mit Ihnen gescoped.

Pentest buchen

Improper Export of Android Application Components

What is CWE-926?

Real-world CVEs caused by CWE-926

Angreiferpfad Schritt für Schritt

Vulnerable XML

Secure pseudo

How to prevent CWE-926

How to detect CWE-926

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-926

Improper Authorization

Exposure of Sensitive Information Through Metadata

Improper Restriction of Software Interfaces to Hardware Features

Unprotected Confidential Information on Device is Accessible by OSAT Vendors

Security Version Number Mutable to Older Versions

Files or Directories Accessible to External Parties

Incorrect Permission Assignment for Critical Resource

Missing Authorization

Incorrect Authorization

Further reading

Bereit zu validieren, was zählt.

Prüfen Sie, ob AI Swarm Pentest zu Ihrer Umgebung passt.

Anfrage erhalten. Nächsten Schritt buchen.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`