Google Android prior 5.0.2/5.1.1/6.0/6.0.1/7.0 Telephony Emergency access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as problematic. The impacted element is an unknown function of the component Telephony. The manipulation leads to access control (Emergency). This vulnerability is traded as CVE-2016-3898. An attack has to be approached locally. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Android (Smartphone Operating System). It has been rated as problematic. This issue affects an unknown code block of the component Telephony. The manipulation with an unknown input leads to a access control vulnerability (Emergency). Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is availability.
The weakness was shared 09/06/2016 as Android Security Bulletin - September 2016 as confirmed security bulletin (Website). It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2016-3898 since 03/30/2016. Attacking locally is a requirement. The requirement for exploitation is a simple authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Upgrading to version 5.0.2, 5.1.1, 6.0, 6.0.1 or 7.0 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The entries VDB-91415, VDB-91416, VDB-91417 and VDB-91418 are related to this item. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: EmergencyClass: Access control / Emergency
CWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Android 5.0.2/5.1.1/6.0/6.0.1/7.0
Timeline
03/30/2016 🔍09/06/2016 🔍
09/06/2016 🔍
09/11/2016 🔍
09/11/2016 🔍
09/15/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - September 2016
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3898 (🔍)
GCVE (CVE): GCVE-0-2016-3898
GCVE (VulDB): GCVE-100-91439
SecurityTracker: 1036763
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 09/11/2016 12:29Updated: 09/15/2022 14:19
Changes: 09/11/2016 12:29 (53), 04/14/2019 09:23 (10), 09/15/2022 14:19 (5)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.