| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android up to 5.1.0. It has been declared as critical. Affected by this issue is some unknown functionality of the component libstagefright. Such manipulation leads to memory corruption. This vulnerability is documented as CVE-2015-3868. Additionally, an exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Google Android up to 5.1.0 (Smartphone Operating System). Affected by this issue is some unknown processing 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. 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 23270724.
The weakness was released 10/29/2015 as 23270724 (Packetstorm). The advisory is available at packetstormsecurity.com. This vulnerability is handled as CVE-2015-3868 since 05/12/2015. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at packetstormsecurity.com. It is declared as proof-of-concept. As 0-day the estimated underground price was around $100k and more.
Upgrading to version 5.1.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (107733) and Vulnerability Center (SBV-53227†). Entries connected to this vulnerability are available at VDB-78270, VDB-78269, VDB-78268 and VDB-78267. 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: 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: 🔍
Upgrade: Android 5.1.1
Timeline
05/12/2015 🔍10/05/2015 🔍
10/06/2015 🔍
10/06/2015 🔍
10/07/2015 🔍
10/29/2015 🔍
06/22/2024 🔍
Sources
Vendor: google.comAdvisory: 23270724
Status: Confirmed
CVE: CVE-2015-3868 (🔍)
GCVE (CVE): GCVE-0-2015-3868
GCVE (VulDB): GCVE-100-78266
X-Force: 107733 - Google Android Libstagefright integer overflow
Vulnerability Center: 53227 - Google Android before 5.1.1 LMY48T Remote Code Execution Vulnerability in libstagefright - CVE-2015-3868, Critical
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/07/2015 10:10Updated: 06/22/2024 05:14
Changes: 10/07/2015 10:10 (54), 03/01/2018 08:25 (7), 06/22/2024 05:14 (24)
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.