Apple watchOS up to 6.0.1 WebKit Universal cross site scripting

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apple watchOS up to 6.0.1 and classified as critical. This affects an unknown function of the component WebKit. The manipulation leads to cross site scripting (Universal). This vulnerability is documented as CVE-2019-8764. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Apple watchOS up to 6.0.1 (Smartwatch Operating System) and classified as critical. This issue affects an unknown part of the component WebKit. The manipulation with an unknown input leads to a cross site scripting vulnerability (Universal). Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
A logic issue was addressed with improved state management. This issue is fixed in watchOS 6.1. Processing maliciously crafted web content may lead to universal cross site scripting.
The weakness was released 10/29/2019 by Sergei Glazunov with Google Project Zero as HT210724 as confirmed advisory (Website). The advisory is shared at support.apple.com. The identification of this vulnerability is CVE-2019-8764. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue. The advisory points out:
A logic issue was addressed with improved state management.
Upgrading to version 6.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Entries connected to this vulnerability are available at VDB-144570, VDB-144571, VDB-144572 and VDB-144573. 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: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
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
Name: UniversalClass: Cross site scripting / Universal
CWE: CWE-79 / CWE-94 / CWE-74
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: watchOS 6.1
Timeline
02/18/2019 🔍10/29/2019 🔍
10/29/2019 🔍
10/31/2019 🔍
01/31/2024 🔍
Sources
Vendor: apple.comAdvisory: HT210724
Researcher: Sergei Glazunov
Organization: Google Project Zero
Status: Confirmed
CVE: CVE-2019-8764 (🔍)
GCVE (CVE): GCVE-0-2019-8764
GCVE (VulDB): GCVE-100-144581
See also: 🔍
Entry
Created: 10/31/2019 08:26Updated: 01/31/2024 11:13
Changes: 10/31/2019 08:26 (49), 10/31/2019 08:31 (17), 01/31/2024 11:13 (4)
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.