| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apple Watch up to 1.0.2 and classified as problematic. This impacts an unknown function of the component IOMobileFrameBuffer. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2015-5843. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Apple Watch up to 1.0.2 (Smartwatch Operating System). It has been declared as critical. Affected by this vulnerability is an unknown part of the component IOMobileFrameBuffer. 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:
IOMobileFrameBuffer 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 shared 09/23/2015 by Filippo Bigarella (beist) as HT205213 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is known as CVE-2015-5843 since 08/06/2015. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The advisory points out:
A memory corruption issue existed in IOMobileFrameBuffer. 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-52891†). The entries VDB-9015, VDB-68413, VDB-77828 and VDB-77762 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.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-5843 (🔍)
GCVE (CVE): GCVE-0-2015-5843
GCVE (VulDB): GCVE-100-78109
SecurityFocus: 76764 - Apple iOS APPLE-SA-2015-09-16-1 Multiple Security Vulnerabilities
SecurityTracker: 1033609
Vulnerability Center: 52891 - Apple watchOS <2 Local Code Execution in IOMobileFrameBuffer, High
See also: 🔍
Entry
Created: 09/28/2015 10:06Updated: 06/19/2022 12:57
Changes: 09/28/2015 10:06 (56), 01/03/2018 09:48 (12), 06/19/2022 12:57 (3)
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.