Google Android up to 5.1.0 Bitmap.cpp Bitmap_createFromParcel numeric error
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Google Android up to 5.1.0. The impacted element is the function Bitmap_createFromParcel of the file core/jni/android/graphics/Bitmap.cpp. The manipulation results in numeric error.
This vulnerability is reported as CVE-2015-1536. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability was found in Google Android up to 5.1.0 (Smartphone Operating System). It has been classified as critical. Affected is the function Bitmap_createFromParcel of the file core/jni/android/graphics/Bitmap.cpp. The manipulation with an unknown input leads to a numeric error vulnerability. CWE is classifying the issue as CWE-189. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Integer overflow in the Bitmap_createFromParcel function in core/jni/android/graphics/Bitmap.cpp in Android before 5.1.1 LMY48I allows attackers to cause a denial of service (system_server crash) or obtain sensitive system_server memory-content information via a crafted application that leverages improper unmarshalling of bitmaps, aka internal bug 19666945.
The weakness was disclosed 10/01/2015 as 19666945 (Website). The advisory is available at groups.google.com. This vulnerability is traded as CVE-2015-1536 since 02/06/2015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
Upgrading to version 5.1.1 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-53207†). The entries VDB-78163, VDB-78164, VDB-78165 and VDB-78166 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit 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: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Numeric errorCWE: CWE-189
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Android 5.1.1
Timeline
02/06/2015 🔍04/21/2015 🔍
09/30/2015 🔍
09/30/2015 🔍
10/01/2015 🔍
10/01/2015 🔍
10/04/2015 🔍
02/03/2018 🔍
Sources
Vendor: google.comAdvisory: 19666945
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2015-1536 (🔍)
GCVE (CVE): GCVE-0-2015-1536
GCVE (VulDB): GCVE-100-78162
Vulnerability Center: 53207 - Google Android before 5.1.1 LMY48I Remote DoS or Information Disclosure Vulnerabilities - CVE-2015-1536, High
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/01/2015 15:09Updated: 02/03/2018 10:21
Changes: 10/01/2015 15:09 (61), 02/03/2018 10:21 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.