CWE-927 隐式意图在敏感通信中的使用
Use of Implicit Intent for Sensitive Communication
结构: Simple
Abstraction: Variant
状态: Incomplete
被利用可能性: unkown
基本描述
The Android application uses an implicit intent for transmitting sensitive data to other applications.
扩展描述
Since an implicit intent does not specify a particular application to receive the data, any application can process the intent by using an Intent Filter for that intent. This can allow untrusted applications to obtain sensitive data. There are two variations on the standard broadcast intent, ordered and sticky.
Ordered broadcast intents are delivered to a series of registered receivers in order of priority as declared by the Receivers. A malicious receiver can give itself a high priority and cause a denial of service by stopping the broadcast from propagating further down the chain. There is also the possibility of malicious data modification, as a receiver may also alter the data within the Intent before passing it on to the next receiver. The downstream components have no way of asserting that the data has not been altered earlier in the chain.
Sticky broadcast intents remain accessible after the initial broadcast. An old sticky intent will be broadcast again to any new receivers that register for it in the future, greatly increasing the chances of information exposure over time. Also, sticky broadcasts cannot be protected by permissions that may apply to other kinds of intents.
In addition, any broadcast intent may include a URI that references data that the receiving component does not normally have the privileges to access. The sender of the intent can include special privileges that grant the receiver read or write access to the specific URI included in the intent. A malicious receiver that intercepts this intent will also gain those privileges and be able to read or write the resource at the specified URI.
相关缺陷
-
cwe_Nature: ChildOf cwe_CWE_ID: 285 cwe_View_ID: 1000 cwe_Ordinal: Primary
-
cwe_Nature: ChildOf cwe_CWE_ID: 285 cwe_View_ID: 699 cwe_Ordinal: Primary
-
cwe_Nature: ChildOf cwe_CWE_ID: 668 cwe_View_ID: 1000
适用平台
Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}
Paradigm: {'cwe_Name': 'Mobile', 'cwe_Prevalence': 'Undetermined'}
常见的影响
| 范围 | 影响 | 注释 |
|---|---|---|
| Confidentiality | Read Application Data | Other applications, possibly untrusted, can read the data that is offered through the Intent. |
| Integrity | Varies by Context | The application may handle responses from untrusted applications on the device, which could cause it to perform unexpected or unauthorized actions. |
可能的缓解方案
Implementation
策略:
If the application only requires communication with its own components, then the destination is always known, and an explicit intent could be used.
示例代码
例
This application wants to create a user account in several trusted applications using one broadcast intent:
bad Java
intent.setAction("com.example.CreateUser");
intent.putExtra("Username", uname_string);
intent.putExtra("Password", pw_string);
sendBroadcast(intent);
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:
attack Java
MyReceiver receiver = new MyReceiver();
registerReceiver(receiver, filter);
When a broadcast contains sensitive information, create a whitelist of applications that can receive the action using the application's manifest file, or programmatically send the intent to each individual intended receiver.
例
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:
bad Java
intent.setAction("com.example.service.UserExists");
intent.putExtra("Username", uname_string);
sendStickyBroadcast(intent);
attack Java
MyReceiver receiver = new MyReceiver();
registerReceiver(receiver, filter);
Sticky broadcasts can be read by any application at any time, and so should never contain sensitive information such as a username.
例
This application is sending an ordered broadcast, asking other applications to open a URL:
bad Java
intent.setAction("com.example.OpenURL");
intent.putExtra("URL_TO_OPEN", url_string);
sendOrderedBroadcastAsUser(intent);
Any application in the broadcast chain may alter the data within the intent. This malicious application is altering the URL to point to an attack site:
attack Java
public void onReceive(Context context, Intent intent) {
attackURL = "www.example.com/attack?" + Url;
setResultData(attackURL);
}
}
The final receiving application will then open the attack URL. Where possible, send intents to specific trusted applications instead of using a broadcast chain.
例
This application sends a special intent with a flag that allows the receiving application to read a data file for backup purposes.
bad Java
intent.setAction("com.example.BackupUserData");
intent.setData(file_uri);
intent.addFlags(FLAG_GRANT_READ_URI_PERMISSION);
sendBroadcast(intent);
attack Java
public void onReceive(Context context, Intent intent) {
stealUserData(userData);
}
}
Any malicious application can register to receive this intent. Because of the FLAG_GRANT_READ_URI_PERMISSION included with the intent, the malicious receiver code can read the user's data.
Notes
引用
文章来源于互联网:scap中文网
- 左青龙
- 微信扫一扫
-
- 右白虎
- 微信扫一扫
-
评论