CWE-925: Improper Verification of Intent by Broadcast Receiver
Presentation Filter:
 DescriptionThe Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source. Extended DescriptionCertain types of Intents, identified by action string, can only be broadcast by the operating system itself, not by third-party applications. However, when an application registers to receive these implicit system intents, it is also registered to receive any explicit intents. While a malicious application cannot send an implicit system intent, it can send an explicit intent to the target application, which may assume that any received intent is a valid implicit system intent and not an explicit intent from another application. This may lead to unintended behavior. Alternate Terms
RelationshipsThe table(s) below shows the weaknesses and high level categories that are related to this weakness. These relationships are defined as ChildOf, ParentOf, MemberOf and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as PeerOf and CanAlsoBe are defined to show similar weaknesses that the user may want to explore. Relevant to the view "Research Concepts" (CWE-1000)
Modes Of IntroductionThe different Modes of Introduction provide information about how and when this weakness may be introduced. The Phase identifies a point in the life cycle at which introduction may occur, while the Note provides a typical scenario related to introduction during the given phase.
Applicable PlatformsThe listings below show possible areas for which the given weakness could appear. These may be for specific named Languages, Operating Systems, Architectures, Paradigms, Technologies, or a class of such platforms. The platform is listed along with how frequently the given weakness appears for that instance. Languages Class: Language-Independent (Undetermined Prevalence) Technologies Class: Mobile (Undetermined Prevalence) Common ConsequencesThe table below specifies different individual consequences associated with the weakness. The Scope identifies the application security area that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in exploiting this weakness. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a weakness will be exploited to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.
Demonstrative ExamplesExample 1 The following example demonstrates the weakness. (bad code) Example Language: XML <manifest package="com.example.vulnerableApplication">
<application>
... <receiver android:name=".ShutdownReceiver">
<intent-filter> </receiver><action android:name="android.intent.action.ACTION_SHUTDOWN" /> </intent-filter>... </application> The ShutdownReceiver class will handle the intent: (bad code) Example Language: Java ... IntentFilter filter = new IntentFilter(Intent.ACTION_SHUTDOWN); BroadcastReceiver sReceiver = new ShutDownReceiver(); registerReceiver(sReceiver, filter); ... public class ShutdownReceiver extends BroadcastReceiver { @Override }public void onReceive(final Context context, final Intent intent) { mainActivity.saveLocalData(); }mainActivity.stopActivity(); 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: (attack code) Example Language: Java window.location = examplescheme://method?parameter=value
An attacker can use this behavior to cause a denial of service. Potential Mitigations
NotesMaintenance This entry will be made more comprehensive in later CWE versions. Related Attack Patterns
References
Content History
More information is available — Please select a different filter. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Use of the Common Weakness Enumeration (CWE) and the associated references from this website are subject to the Terms of Use. CWE is sponsored by the U.S. Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA) and managed by the Homeland Security Systems Engineering and Development Institute (HSSEDI) which is operated by The MITRE Corporation (MITRE). Copyright © 2006-2021, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation. |
|
