Google Android up to 5.1.0 libstagefright MPEG4Extractor.cpp NAL memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in Google Android up to 5.1.0 and classified as critical. Affected is an unknown function of the file MPEG4Extractor.cpp of the component libstagefright. Performing a manipulation of the argument NAL as part of MP4 File results in memory corruption. This vulnerability is known as CVE-2015-3832. No exploit is available. The affected component should be upgraded.
Details
A vulnerability classified as very critical has been found in Google Android up to 5.1.0 (Smartphone Operating System). This affects an unknown part of the file MPEG4Extractor.cpp of the component libstagefright. The manipulation of the argument NAL as part of a MP4 File leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Multiple buffer overflows in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I allow remote attackers to execute arbitrary code via invalid size values of NAL units in MP4 data, aka internal bug 19641538.
The weakness was published 10/01/2015 as 19641538 (Website). The advisory is shared at groups.google.com. This vulnerability is uniquely identified as CVE-2015-3832 since 05/12/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/03/2018). It is expected to see the exploit prices for this product increasing in the near future.
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-53201†). Similar entries are available at VDB-78162, VDB-78163, VDB-78164 and VDB-78166. 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: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Android 5.1.1
Timeline
04/21/2015 🔍05/12/2015 🔍
09/30/2015 🔍
09/30/2015 🔍
10/01/2015 🔍
10/01/2015 🔍
10/04/2015 🔍
02/03/2018 🔍
Sources
Vendor: google.comAdvisory: 19641538
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2015-3832 (🔍)
GCVE (CVE): GCVE-0-2015-3832
GCVE (VulDB): GCVE-100-78165
Vulnerability Center: 53201 - Google Android before 5.1.1 LMY48I Remote Code Execution via Crafted MP4 Data - CVE-2015-3832, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/01/2015 15:10Updated: 02/03/2018 10:19
Changes: 10/01/2015 15:10 (56), 02/03/2018 10:19 (8)
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.