Google Android 8.0/8.1 CmapCoverage.cpp getVSCoverage out-of-bounds
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 8.0/8.1 and classified as problematic. This vulnerability affects the function getVSCoverage of the file CmapCoverage.cpp. Executing a manipulation can lead to out-of-bounds.
This vulnerability is handled as CVE-2017-13275. It is possible to launch the attack on the local host. There is not any exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Google Android 8.0/8.1 (Smartphone Operating System). It has been declared as problematic. This vulnerability affects the function getVSCoverage of the file CmapCoverage.cpp. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. CVE summarizes:
In getVSCoverage of CmapCoverage.cpp, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional privileges needed. User interaction is needed for exploitation. Product: Android. Versions: 8.0, 8.1. Android ID: A-70808908.
The bug was discovered 04/05/2018. The weakness was released 04/04/2018 (Website). The advisory is shared for download at source.android.com. This vulnerability was named CVE-2017-13275 since 08/23/2017. The attack needs to be approached locally. A single authentication is needed for exploitation. There are known technical details, but no exploit is available.
Applying a patch is able to eliminate this problem.
Entries connected to this vulnerability are available at VDB-83180, VDB-115633, VDB-115638 and VDB-115639. Once again VulDB remains the best source for 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: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: Out-of-boundsCWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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 🔍04/04/2018 🔍
04/04/2018 🔍
04/05/2018 🔍
04/05/2018 🔍
01/21/2020 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-13275 (🔍)
GCVE (CVE): GCVE-0-2017-13275
GCVE (VulDB): GCVE-100-115756
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 04/05/2018 09:26Updated: 01/21/2020 20:04
Changes: 04/05/2018 09:26 (60), 01/21/2020 20:04 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.