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-925 Variante Incomplet
Improper Verification of Intent by Broadcast Receiver
This vulnerability occurs when an Android app's Broadcast Receiver accepts an Intent without confirming it originated from a trusted, authorized source, such as the operating system.
Définition
What is CWE-925?
This vulnerability occurs when an Android app's Broadcast Receiver accepts an Intent without confirming it originated from a trusted, authorized source, such as the operating system.
Android allows apps to register Broadcast Receivers for specific system-generated Intents, like a device boot completion. These are implicit intents that, by design, should only be sent by the OS. However, the same receiver registration also accepts explicit intents, which can be crafted and sent by any app on the device.
A malicious app can exploit this by sending a carefully crafted explicit intent to the receiver. If the receiving app fails to verify the intent's source, it may incorrectly process the malicious intent as a legitimate system broadcast. This confusion can trigger unauthorized actions, expose sensitive data, or crash the application.
Impact réel
Real-world CVEs caused by CWE-925
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
The following example demonstrates the weakness.
- 2
The ShutdownReceiver class will handle the intent:
- 3
Because the method does not confirm that the intent action is the expected system intent, any received intent will trigger the shutdown procedure, as shown here:
- 4
An attacker can use this behavior to cause a denial of service.
Exemple de code vulnérable
Vulnerable XML
The following example demonstrates the weakness.
<manifest package="com.example.vulnerableApplication">
<application>
```
...*
```
<receiver android:name=".ShutdownReceiver">
<intent-filter>
<action android:name="android.intent.action.ACTION_SHUTDOWN" />
</intent-filter>
</receiver>
```
...*
</application></manifest> Charge utile de l'attaquant
Because the method does not confirm that the intent action is the expected system intent, any received intent will trigger the shutdown procedure, as shown here:
window.location = examplescheme://method?parameter=value 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-925
- Architecture and Design Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.
Signaux de détection
How to detect CWE-925
CWE-925
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.
Questions fréquentes Qu'est-ce que CWE-925 ?
Quelle est la gravité de CWE-925 ?
Quels langages ou plateformes sont affectés par CWE-925 ?
Comment puis-je prévenir CWE-925 ?
Comment Plexicus détecte et corrige CWE-925 ?
Où puis-je en savoir plus sur CWE-925 ?
Frequently asked questions
Qu'est-ce que CWE-925 ?
This vulnerability occurs when an Android app's Broadcast Receiver accepts an Intent without confirming it originated from a trusted, authorized source, such as the operating system.
Quelle est la gravité de CWE-925 ?
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-925 ?
MITRE lists the following affected platforms: Mobile.
Comment puis-je prévenir CWE-925 ?
Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.
Comment Plexicus détecte et corrige CWE-925 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-925 à 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-925 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/925.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Prêt à valider l'essentiel ?
Prêt à valider ce qui compte.
Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.