CWE-927 Variante Incompleto

Use of Implicit Intent for Sensitive Communication

This vulnerability occurs when an Android app uses an implicit intent to send sensitive data, allowing any other app on the device to potentially intercept and read that information.

Definición

What is CWE-927?

This vulnerability occurs when an Android app uses an implicit intent to send sensitive data, allowing any other app on the device to potentially intercept and read that information.
Implicit intents are a security risk because they don't specify a single recipient app. Instead, they broadcast data to any application that declares it can handle that type of intent. This means a malicious app with a matching intent filter can eavesdrop on sensitive communications, such as authentication tokens or personal data. The risk is amplified by two specific broadcast types: ordered broadcasts, where a high-priority malicious receiver can block or alter the data mid-chain, and sticky broadcasts, which persist data in the system long after the initial send, increasing the window for exposure. Furthermore, intents can grant temporary URI permissions, giving the receiver access to files or content the sender app protects. A malicious interceptor gains those same privileges, leading to unauthorized data access. Identifying and fixing every instance of this pattern in a large codebase is challenging. An ASPM platform like Plexicus can automatically detect these flaws via SAST, and its AI-powered remediation can suggest the specific code changes—like switching to explicit intents or protected broadcasts—saving significant manual review time.
Impacto en el mundo real

Real-world CVEs caused by CWE-927

  • CVE-2022-4903

    An Android application does not use FLAG_IMMUTABLE when creating a PendingIntent.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    This application wants to create a user account in several trusted applications using one broadcast intent:

  2. 2

    This application assumes only the trusted applications will be listening for the action. A malicious application can register for this action and intercept the user's login information, as below:

  3. 3

    When a broadcast contains sensitive information, create an allowlist of applications that can receive the action using the application's manifest file, or programmatically send the intent to each individual intended receiver.

  4. 4

    This application interfaces with a web service that requires a separate user login. It creates a sticky intent, so that future trusted applications that also use the web service will know who the current user is:

  5. 5

    Sticky broadcasts can be read by any application at any time, and so should never contain sensitive information such as a username.

Ejemplo de código vulnerable

Vulnerable Java

This application wants to create a user account in several trusted applications using one broadcast intent:

Vulnerable Java 
Intent intent = new Intent();
  intent.setAction("com.example.CreateUser");
  intent.putExtra("Username", uname_string);
  intent.putExtra("Password", pw_string);
  sendBroadcast(intent);
Payload del atacante

This application assumes only the trusted applications will be listening for the action. A malicious application can register for this action and intercept the user's login information, as below:

Payload del atacante Java 
IntentFilter filter = new IntentFilter("com.example.CreateUser");
  MyReceiver receiver = new MyReceiver();
  registerReceiver(receiver, filter);
Ejemplo de código seguro

Secure pseudo

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

  • Implementation If the application only requires communication with its own components, then the destination is always known, and an explicit intent could be used.
Señales de detección

How to detect CWE-927

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

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-927 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-927?

This vulnerability occurs when an Android app uses an implicit intent to send sensitive data, allowing any other app on the device to potentially intercept and read that information.

¿Qué gravedad tiene CWE-927?

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

MITRE lists the following affected platforms: Mobile.

¿Cómo puedo prevenir CWE-927?

If the application only requires communication with its own components, then the destination is always known, and an explicit intent could be used.

¿Cómo detecta y corrige Plexicus CWE-927?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-927 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-927?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/927.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-927

CWE-285 Padre

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo