| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Apple iOS up to 12.3.2. It has been classified as critical. The affected element is an unknown function of the component Core Data. This manipulation causes memory corruption. This vulnerability is handled as CVE-2019-8660. The attack can be initiated remotely. Additionally, an exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in Apple iOS up to 12.3.2 (Smartphone Operating System). It has been declared as critical. Affected by this vulnerability is an unknown code block of the component Core Data. 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 weakness was released 07/22/2019 by Natalie Silvanovich with Google Project Zero as HT210346 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is known as CVE-2019-8660 since 02/18/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The advisory points out:
A memory corruption issue was addressed with improved input validation.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.
Upgrading to version 12.4 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). Entries connected to this vulnerability are available at VDB-138539, VDB-138565, VDB-138629 and VDB-138659. 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: 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: iOS 12.4
Timeline
02/18/2019 🔍07/22/2019 🔍
07/22/2019 🔍
07/24/2019 🔍
01/25/2025 🔍
Sources
Vendor: apple.comAdvisory: HT210346
Researcher: Natalie Silvanovich
Organization: Google Project Zero
Status: Confirmed
CVE: CVE-2019-8660 (🔍)
GCVE (CVE): GCVE-0-2019-8660
GCVE (VulDB): GCVE-100-138661
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 07/24/2019 16:02Updated: 01/25/2025 12:31
Changes: 07/24/2019 16:02 (64), 07/11/2020 09:59 (1), 11/07/2023 09:17 (4), 01/25/2025 12:31 (22)
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.