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-927 Variant Incomplete
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.
Definition
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.
Real-world impact
Real-world CVEs caused by CWE-927
-
An Android application does not use FLAG_IMMUTABLE when creating a PendingIntent.
How attackers exploit it
Step-by-step attacker path
- 1
This application wants to create a user account in several trusted applications using one broadcast intent:
- 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
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
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
Sticky broadcasts can be read by any application at any time, and so should never contain sensitive information such as a username.
Vulnerable code example
Vulnerable Java
This application wants to create a user account in several trusted applications using one broadcast intent:
Intent intent = new Intent();
intent.setAction("com.example.CreateUser");
intent.putExtra("Username", uname_string);
intent.putExtra("Password", pw_string);
sendBroadcast(intent); Attacker payload
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:
IntentFilter filter = new IntentFilter("com.example.CreateUser");
MyReceiver receiver = new MyReceiver();
registerReceiver(receiver, filter); Secure code example
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.
Prevention checklist
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.
Detection signals
How to detect CWE-927
Plexicus auto-detects CWE-927 and opens a fix PR in under 60 seconds.
Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.
Frequently asked questions What is CWE-927?
How serious is CWE-927?
What languages or platforms are affected by CWE-927?
How can I prevent CWE-927?
How does Plexicus detect and fix CWE-927?
Where can I learn more about CWE-927?
Frequently asked questions
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.
How serious is CWE-927?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-927?
MITRE lists the following affected platforms: Mobile.
How can I prevent 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.
How does Plexicus detect and fix CWE-927?
Plexicus's SAST engine matches the data-flow signature for CWE-927 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-927?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/927.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-927
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 Sibling
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 Sibling
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 Sibling
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 Sibling
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 Sibling
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 Sibling
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 Sibling
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 Sibling
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…
Resources
Further reading
Ready when you are
Don't Let Security
Weigh You Down.
Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.