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 Variante Incomplet
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…
Définition
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.
Impact réel
Real-world CVEs caused by CWE-926
Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 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.
Exemple de code vulnérable
Vulnerable XML
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> Exemple de code sécurisé
Secure 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.
Liste de contrôle de prévention
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.
Signaux de détection
How to detect CWE-926
Plexicus détecte automatiquement CWE-926 et ouvre une PR de correction en moins de 60 secondes.
Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.
Questions fréquentes Qu'est-ce que CWE-926 ?
Quelle est la gravité de CWE-926 ?
Quels langages ou plateformes sont affectés par CWE-926 ?
Comment puis-je prévenir CWE-926 ?
Comment Plexicus détecte et corrige CWE-926 ?
Où puis-je en savoir plus sur CWE-926 ?
Frequently asked questions
Qu'est-ce que 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.
Quelle est la gravité de CWE-926 ?
MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.
Quels langages ou plateformes sont affectés par CWE-926 ?
MITRE lists the following affected platforms: Mobile.
Comment puis-je prévenir CWE-926 ?
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.
Comment Plexicus détecte et corrige CWE-926 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-926 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.
Où puis-je en savoir plus sur CWE-926 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/926.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-926
CWE-285 Parent
Improper Authorization
This vulnerability occurs when an application fails to properly verify whether a user has permission to access specific data or perform…
CWE-1230 Frère
Exposure of Sensitive Information Through Metadata
This vulnerability occurs when an application protects the primary source of sensitive data but fails to secure the metadata derived from…
CWE-1256 Frère
Improper Restriction of Software Interfaces to Hardware Features
This vulnerability occurs when a system's software interfaces to hardware features—like power, clock, or performance management—are not…
CWE-1297 Frère
Unprotected Confidential Information on Device is Accessible by OSAT Vendors
This vulnerability occurs when a semiconductor chip does not properly secure sensitive data, making it accessible to third-party…
CWE-1328 Frère
Security Version Number Mutable to Older Versions
This vulnerability occurs when a hardware system's security version number can be changed, allowing an attacker to downgrade or roll back…
CWE-552 Frère
Files or Directories Accessible to External Parties
This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.
CWE-732 Frère
Incorrect Permission Assignment for Critical Resource
This vulnerability occurs when a system grants overly permissive access to a sensitive resource, allowing unauthorized users or processes…
CWE-862 Frère
Missing Authorization
This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain…
CWE-863 Frère
Incorrect Authorization
This vulnerability occurs when an application checks if a user is allowed to perform an action or access data, but the check is flawed or…
Prêt quand vous l'êtes
Arrêtez de payer par développeur.
Commencez à fermer la boucle.
Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.