| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical was found in Google Android up to 5.1.0. Affected by this issue is some unknown functionality of the component libstagefright. The manipulation results in memory corruption. This vulnerability was named CVE-2015-7716. There is no available exploit. 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 an unknown function of the component libstagefright. The manipulation with an unknown input 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. CVE summarizes:
libstagefright in Android 5.x before 5.1.1 LMY48T allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted media file, aka internal bug 20721050, a different vulnerability than CVE-2015-3873.
The weakness was presented 10/06/2015 as 20721050 (Website). The advisory is shared for download at groups.google.com. This vulnerability is traded as CVE-2015-7716 since 10/06/2015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 02/13/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.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-53534†). See VDB-78261, VDB-78262, VDB-78263 and VDB-78264 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 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
10/06/2015 🔍10/06/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/07/2015 🔍
10/18/2015 🔍
02/13/2018 🔍
Sources
Vendor: google.comAdvisory: 20721050
Status: Confirmed
CVE: CVE-2015-7716 (🔍)
GCVE (CVE): GCVE-0-2015-7716
GCVE (VulDB): GCVE-100-78288
Vulnerability Center: 53534 - Google Android before 5.1.1 LMY48T Remote Code Execution Vulnerability in libstagefright - CVE-2015-7716, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/07/2015 10:13Updated: 02/13/2018 07:47
Changes: 10/07/2015 10:13 (51), 02/13/2018 07:47 (7)
Complete: 🔍
Cache ID: 216:0E0: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.