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 Incompleto
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.
Definición
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.
Impacto en el mundo real
Real-world CVEs caused by CWE-925
Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 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.
Ejemplo de código vulnerable
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> Payload del atacante
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 Ejemplo de código seguro
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.
Lista de prevención
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.
Señales de detección
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.
Preguntas frecuentes ¿Qué es CWE-925?
¿Qué gravedad tiene CWE-925?
¿Qué lenguajes o plataformas se ven afectados por CWE-925?
¿Cómo puedo prevenir CWE-925?
¿Cómo detecta y corrige Plexicus CWE-925?
¿Dónde puedo aprender más sobre CWE-925?
Frequently asked questions
¿Qué es 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.
¿Qué gravedad tiene CWE-925?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-925?
MITRE lists the following affected platforms: Mobile.
¿Cómo puedo prevenir CWE-925?
Before acting on the Intent, check the Intent Action to make sure it matches the expected System action.
¿Cómo detecta y corrige Plexicus CWE-925?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-925 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-925?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/925.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-925
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.