| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android up to 8.1. This affects an unknown part of the component Media Framework. This manipulation causes memory corruption. This vulnerability is handled as CVE-2017-13177. The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as critical was found in Google Android up to 8.1 (Smartphone Operating System). Affected by this vulnerability is some unknown functionality of the component Media Framework. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 01/05/2018. The weakness was released 01/02/2018 with Trend Micro as Android Security Bulletin - January 2018 as confirmed security bulletin (Website). The advisory is shared at source.android.com. This vulnerability is known as CVE-2017-13177 since 08/23/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/28/2021). It is expected to see the exploit prices for this product increasing in the near future.
Applying a patch is able to eliminate this problem. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 102414†) and SecurityTracker (ID 1040106†). Entries connected to this vulnerability are available at VDB-111420, VDB-111439, VDB-111438 and VDB-111437. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
08/23/2017 🔍01/01/2018 🔍
01/02/2018 🔍
01/02/2018 🔍
01/05/2018 🔍
01/05/2018 🔍
01/07/2018 🔍
01/12/2018 🔍
01/28/2021 🔍
Sources
Vendor: google.comAdvisory: Android Security Bulletin - January 2018
Researcher: Hongli Han
Organization: Trend Micro
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-13177 (🔍)
GCVE (CVE): GCVE-0-2017-13177
GCVE (VulDB): GCVE-100-111421
SecurityFocus: 102414 - Google Android Media Framework Component Multiple Security Vulnerabilities
SecurityTracker: 1040106
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 01/07/2018 11:30Updated: 01/28/2021 18:22
Changes: 01/07/2018 11:30 (67), 12/20/2019 08:34 (6), 01/28/2021 18:16 (3), 01/28/2021 18:22 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.