Google Android Camera Driver video_ioctl2 null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been declared as problematic. This issue affects the function video_ioctl2 of the component Camera Driver. Executing a manipulation can lead to null pointer dereference.
This vulnerability is registered as CVE-2017-15846. The attack needs to be launched locally. No exploit is available.
Applying a patch is advised to resolve this issue.
Details
A vulnerability has been found in Google Android (Smartphone Operating System) (version now known) and classified as problematic. This vulnerability affects the function video_ioctl2 of the component Camera Driver. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:
In the video_ioctl2() function in the camera driver in Android for MSM, Firefox OS for MSM, and QRD Android before 2017-09-16, an untrusted pointer dereference may potentially occur.
The bug was discovered 02/05/2018. The weakness was published 03/30/2018 (Website). The advisory is shared for download at source.android.com. This vulnerability was named CVE-2017-15846 since 10/24/2017. The exploitation appears to be easy. The attack needs to be approached locally. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 53 days. During that time the estimated underground price was around $5k-$25k.
Applying a patch is able to eliminate this problem.
Similar entries are available at VDB-110104, VDB-113150, VDB-113156 and VDB-113159. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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.5
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: 🔍
Patch: source.codeaurora.org
Timeline
10/24/2017 🔍02/05/2018 🔍
03/30/2018 🔍
03/30/2018 🔍
03/31/2018 🔍
02/24/2023 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-15846 (🔍)
GCVE (CVE): GCVE-0-2017-15846
GCVE (VulDB): GCVE-100-115240
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/31/2018 09:55Updated: 02/24/2023 14:50
Changes: 03/31/2018 09:55 (60), 01/18/2020 10:12 (2), 02/24/2023 14:50 (4)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.