| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Apple watchOS up to 5.2.1. Impacted is an unknown function of the component Core Data. The manipulation leads to memory corruption. This vulnerability is traded as CVE-2019-8660. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Apple watchOS up to 5.2.1 (Smartwatch Operating System). This issue affects some unknown functionality of the component Core Data. 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:
A memory corruption issue was addressed with improved input validation. This issue is fixed in iOS 12.4, macOS Mojave 10.14.6, tvOS 12.4, watchOS 5.3. A remote attacker may be able to cause unexpected application termination or arbitrary code execution.
The weakness was shared 07/22/2019 by Natalie Silvanovich with Google Project Zero as HT210353 as confirmed advisory (Website). It is possible to read the advisory at support.apple.com. The identification of this vulnerability is CVE-2019-8660 since 02/18/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. The advisory points out:
A memory corruption issue was addressed with improved input validation.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 5.3 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (47193). The entries VDB-138537, VDB-138538, VDB-138540 and VDB-138541 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for 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: 8.5VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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 |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: watchOS 5.3
Timeline
02/18/2019 🔍07/22/2019 🔍
07/22/2019 🔍
07/24/2019 🔍
01/24/2025 🔍
Sources
Vendor: apple.comAdvisory: HT210353
Researcher: Natalie Silvanovich
Organization: Google Project Zero
Status: Confirmed
CVE: CVE-2019-8660 (🔍)
GCVE (CVE): GCVE-0-2019-8660
GCVE (VulDB): GCVE-100-138539
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/24/2019 15:01Updated: 01/24/2025 14:28
Changes: 07/24/2019 15:01 (64), 07/10/2020 12:27 (1), 01/24/2025 14:28 (23)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

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