Google Android 5.0.1/5.1/6.0 SurfaceFlinger information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 5.0.1/5.1/6.0. It has been classified as problematic. This impacts an unknown function of the component SurfaceFlinger. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2016-3836. The attack must be carried out locally. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in Google Android 5.0.1/5.1/6.0 (Smartphone Operating System) and classified as problematic. This issue affects an unknown code block of the component SurfaceFlinger. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality.
The weakness was presented 08/01/2016 with Tencent as Android Security Bulletin - August 2016 as confirmed security bulletin (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2016-3836 since 03/30/2016. The exploitation is known to be easy. An attack has to be approached locally. The requirement for exploitation is a simple authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 89 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 5.0.2, 5.1.1, 6.0 or 6.0.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92224†). See VDB-90455, VDB-90456, VDB-90457 and VDB-90458 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
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
Class: Information disclosureCWE: CWE-200 / 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
Timeline
03/30/2016 🔍05/04/2016 🔍
08/01/2016 🔍
08/01/2016 🔍
08/01/2016 🔍
08/05/2016 🔍
08/06/2016 🔍
09/12/2022 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - August 2016
Organization: Tencent
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-3836 (🔍)
GCVE (CVE): GCVE-0-2016-3836
GCVE (VulDB): GCVE-100-90473
SecurityFocus: 92224 - Google Android CVE-2016-3836 Information Disclosure Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 08/06/2016 14:02Updated: 09/12/2022 07:58
Changes: 08/06/2016 14:02 (59), 03/19/2019 08:47 (14), 09/12/2022 07:58 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.