| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android up to 5.1.0. This issue affects some unknown processing of the component libstagefright. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2015-3871. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Google Android up to 5.1.0 (Smartphone Operating System) and classified as critical. This issue affects some unknown functionality of the component libstagefright. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is 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 23031033.
The weakness was shared 10/06/2015 as 23031033 (Website). The advisory is shared at groups.google.com. The identification of this vulnerability is CVE-2015-3871 since 05/12/2015. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly 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.
The vulnerability is also documented in the vulnerability database at Vulnerability Center (SBV-53226†). The entries VDB-78261, VDB-78262, VDB-78263 and VDB-78264 are related to this item. 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: 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
05/12/2015 🔍10/05/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/07/2015 🔍
02/03/2018 🔍
Sources
Vendor: google.comAdvisory: 23031033
Status: Confirmed
CVE: CVE-2015-3871 (🔍)
GCVE (CVE): GCVE-0-2015-3871
GCVE (VulDB): GCVE-100-78269
Vulnerability Center: 53226 - Google Android before 5.1.1 LMY48T Remote Code Execution Vulnerability in libstagefright - CVE-2015-3871, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/07/2015 10:10Updated: 02/03/2018 10:28
Changes: 10/07/2015 10:10 (51), 02/03/2018 10:28 (7)
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.