| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in Apple iOS and iPadOS up to 13.1.3 and classified as critical. This affects an unknown part of the component WebKit. This manipulation causes memory corruption. This vulnerability appears as CVE-2019-8822. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability has been found in Apple iOS and iPadOS up to 13.1.3 (Smartphone Operating System) and classified as critical. Affected by this vulnerability is an unknown part of the component WebKit. 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 presented 10/28/2019 by Sergei Glazunov with Google Project Zero as HT210721 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is known as CVE-2019-8822. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/31/2024). It is expected to see the exploit prices for this product increasing in the near future. The advisory points out:
Multiple memory corruption issues were addressed with improved memory handling.
Upgrading to version 13.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
See VDB-144525, VDB-144528, VDB-144529 and VDB-144530 for similar entries. 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: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: 🔍
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: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: iOS/iPadOS 13.2
Timeline
02/18/2019 🔍10/28/2019 🔍
10/28/2019 🔍
10/31/2019 🔍
01/31/2024 🔍
Sources
Vendor: apple.comAdvisory: HT210721
Researcher: Sergei Glazunov
Organization: Google Project Zero
Status: Confirmed
CVE: CVE-2019-8822 (🔍)
GCVE (CVE): GCVE-0-2019-8822
GCVE (VulDB): GCVE-100-144553
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 10/31/2019 07:37Updated: 01/31/2024 09:20
Changes: 10/31/2019 07:37 (48), 10/31/2019 07:42 (16), 01/31/2024 09:20 (5)
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.