Google Android up to 5.1.1 libstagefright MP3/MP4 File input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $25k-$100k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android up to 5.1.1. Affected is an unknown function of the component libstagefright. This manipulation as part of MP3/MP4 File causes input validation. This vulnerability is tracked as CVE-2015-3876. Moreover, an exploit is present.
Details
A vulnerability has been found in Google Android up to 5.1.1 (Smartphone Operating System) and classified as very critical. Affected by this vulnerability is an unknown code of the component libstagefright. The manipulation as part of a MP3/MP4 File leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
libstagefright in Android through 5.1.1 LMY48M allows remote attackers to execute arbitrary code via crafted metadata in a (1) MP3 or (2) MP4 file.
The weakness was disclosed 10/01/2015 by xeroxnir as not defined tweet (Twitter) via Zimperium. It is possible to read the advisory at twitter.com. The vendor was not involved in the public release. This vulnerability is known as CVE-2015-3876 since 05/12/2015. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a private exploit is available. The pricing for an exploit might be around USD $25k-$100k at the moment (estimation calculated on 06/20/2022). It is expected to see the exploit prices for this product increasing in the near future.
It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Additional details are provided at t.co. The entry VDB-78196 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 1.0
- 1.1
- 1.5
- 1.6
- 2.0
- 2.0.1
- 2.1
- 2.2
- 2.2.1
- 2.2.2
- 2.2.3
- 2.3
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
- 2.3.6
- 2.3.7
- 3.0
- 3.1
- 3.2
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 4.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.1
- 4.1.1
- 4.1.2
- 4.2
- 4.2.1
- 4.2.2
- 4.3
- 4.3.1
- 4.4
- 4.4.1
- 4.4.2
- 4.4.3
- 4.4.4
- 5.0
- 5.0.1
- 5.0.2
- 5.1
- 5.1.1
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.4
VulDB Base Score: 10.0
VulDB Temp Score: 9.4
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Private
Status: Proof-of-Concept
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/12/2015 🔍10/01/2015 🔍
10/01/2015 🔍
10/02/2015 🔍
06/20/2022 🔍
Sources
Vendor: google.comAdvisory: twitter.com
Researcher: xeroxnir
Status: Not defined
CVE: CVE-2015-3876 (🔍)
GCVE (CVE): GCVE-0-2015-3876
GCVE (VulDB): GCVE-100-78187
SecurityTracker: 1033725
scip Labs: https://www.scip.ch/en/?labs.20150917
Misc.: 🔍
See also: 🔍
Entry
Created: 10/02/2015 10:27Updated: 06/20/2022 07:30
Changes: 10/02/2015 10:27 (52), 02/04/2018 10:55 (8), 06/20/2022 07:30 (3)
Complete: 🔍
Cache ID: 216:5B6:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.