| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Apple Watch up to 1.0.2. Impacted is an unknown function of the component IOAcceleratorFamily. Performing a manipulation results in memory corruption. This vulnerability is known as CVE-2015-5848. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Apple Watch up to 1.0.2 (Smartwatch Operating System). This affects some unknown processing of the component IOAcceleratorFamily. 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. The summary by CVE is:
IOAcceleratorFamily in Apple iOS before 9 allows local users to gain privileges or cause a denial of service (memory corruption) via unspecified vectors.
The weakness was published 09/23/2015 by Filippo Bigarella (beist) as HT205213 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is uniquely identified as CVE-2015-5848 since 08/06/2015. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The advisory points out:
A memory corruption issue existed in IOAcceleratorFamily. This issue was addressed through improved memory handling.
Upgrading to version 2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 76764†) and Vulnerability Center (SBV-52887†). Similar entries are available at VDB-9015, VDB-68413, VDB-77828 and VDB-77762. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.9
VulDB Base Score: 9.3
VulDB Temp Score: 8.9
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: Partially
Local: Yes
Remote: No
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: 🔍
Reaction Time: 🔍
Exposure Time: 🔍
Upgrade: Watch 2
Timeline
08/06/2015 🔍09/16/2015 🔍
09/18/2015 🔍
09/21/2015 🔍
09/22/2015 🔍
09/23/2015 🔍
09/23/2015 🔍
09/28/2015 🔍
06/19/2022 🔍
Sources
Vendor: apple.comAdvisory: HT205213
Researcher: Filippo Bigarella (beist)
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2015-5848 (🔍)
GCVE (CVE): GCVE-0-2015-5848
GCVE (VulDB): GCVE-100-78105
SecurityFocus: 76764 - Apple iOS APPLE-SA-2015-09-16-1 Multiple Security Vulnerabilities
SecurityTracker: 1033609
Vulnerability Center: 52887 - Apple watchOS <2 Local Code Execution Vulnerability in IOAcceleratorFamily, High
See also: 🔍
Entry
Created: 09/28/2015 10:06Updated: 06/19/2022 12:27
Changes: 09/28/2015 10:06 (56), 01/03/2018 09:47 (12), 06/19/2022 12:27 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

No comments yet. Languages: en.
Please log in to comment.