| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $5k-$25k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Google Android up to 5.1.0. The affected element is an unknown function of the component libstagefright. The manipulation results in memory corruption. This vulnerability is reported as CVE-2015-6603. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Google Android up to 5.1.0 (Smartphone Operating System). Affected is an unknown functionality 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 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 23227354.
The weakness was disclosed 10/06/2015 as 23227354 (Website). The advisory is available at groups.google.com. This vulnerability is traded as CVE-2015-6603 since 08/21/2015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of 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.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-53230†). The entries VDB-78261, VDB-78262, VDB-78263 and VDB-78264 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: 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
08/21/2015 🔍10/05/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/07/2015 🔍
02/03/2018 🔍
Sources
Vendor: google.comAdvisory: 23227354
Status: Confirmed
CVE: CVE-2015-6603 (🔍)
GCVE (CVE): GCVE-0-2015-6603
GCVE (VulDB): GCVE-100-78282
Vulnerability Center: 53230 - Google Android before 5.1.1 LMY48T Remote Code Execution Vulnerability in libstagefright - CVE-2015-6603, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/07/2015 10:12Updated: 02/03/2018 10:29
Changes: 10/07/2015 10:12 (51), 02/03/2018 10:29 (7)
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.