| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android up to 5.1.0. The impacted element is an unknown function of the component libstagefright. This manipulation causes memory corruption. This vulnerability appears as CVE-2015-6604. In addition, an exploit is available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Google Android up to 5.1.0 (Smartphone Operating System). Affected by this vulnerability is some unknown functionality of the component libstagefright. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
libstagefright in Android 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 23129786.
The weakness was presented 10/06/2015 as 23129786 (Website). It is possible to read the advisory at groups.google.com. This vulnerability is known as CVE-2015-6604 since 08/21/2015. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available.
It is possible to download the exploit at packetstormsecurity.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $100k and more.
Upgrading to version 5.1.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-53228†). See VDB-78261, VDB-78262, VDB-78263 and VDB-78264 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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
08/21/2015 🔍10/05/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/07/2015 🔍
06/22/2024 🔍
Sources
Vendor: google.comAdvisory: 23129786
Status: Confirmed
CVE: CVE-2015-6604 (🔍)
GCVE (CVE): GCVE-0-2015-6604
GCVE (VulDB): GCVE-100-78283
Vulnerability Center: 53228 - Google Android before 5.1.1 LMY48T Remote Code Execution Vulnerability in libstagefright - CVE-2015-6604, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/07/2015 10:12Updated: 06/22/2024 19:17
Changes: 10/07/2015 10:12 (51), 02/03/2018 10:28 (7), 06/22/2024 19:17 (24)
Complete: 🔍
Cache ID: 216::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.