VDB-105221 · CVE-2017-8258 · BID 99465

Google Android Qualcomm Camera Driver out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$5k-$25k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Google Android. The affected element is an unknown function of the component Qualcomm Camera Driver. The manipulation leads to out-of-bounds. This vulnerability is documented as CVE-2017-8258. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Google Android (Smartphone Operating System) (the affected version is unknown). This issue affects an unknown code of the component Qualcomm Camera Driver. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An array out-of-bounds access in all Qualcomm products with Android releases from CAF using the Linux kernel can potentially occur in a camera driver.

The bug was discovered 07/05/2017. The weakness was released 08/11/2017 by Yonggang Guo, Gengjia Chen, Jianqiang Zhao, pjf, Scott Bauer, Derrek, Yuan-Tsung Lo, Xuxian Jiang and Di Shen with Qihoo 360 (Website). The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2017-8258 since 04/25/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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 11/06/2019). It is expected to see the exploit prices for this product increasing in the near future.

The vulnerability was handled as a non-public zero-day exploit for at least 37 days. During that time the estimated underground price was around $25k-$100k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 99465†). Entries connected to this vulnerability are available at VDB-101214, VDB-103224, VDB-103225 and VDB-103226. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/25/2017 🔍
07/05/2017 +71 days 🔍
07/06/2017 +1 days 🔍
08/11/2017 +36 days 🔍
08/11/2017 +0 days 🔍
08/11/2017 +0 days 🔍
11/06/2019 +817 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: source.android.com
Researcher: Yonggang Guo, Gengjia Chen, Jianqiang Zhao, pjf, Scott Bauer, Derrek, Yuan-Tsung Lo, Xuxian Jiang, Di Shen
Organization: Qihoo 360
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-8258 (🔍)
GCVE (CVE): GCVE-0-2017-8258
GCVE (VulDB): GCVE-100-105221
SecurityFocus: 99465 - Google Android Qualcomm Components Multiple Security Vulnerabilities

scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍

Entryinfo

Created: 08/11/2017 21:09
Updated: 11/06/2019 11:28
Changes: 08/11/2017 21:09 (63), 11/06/2019 11:28 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!