| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Apple watchOS up to 8.0.1. Impacted is an unknown function of the component WebKit. This manipulation causes cross-domain policy. The identification of this vulnerability is CVE-2021-30887. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Apple watchOS up to 8.0.1 (Smartwatch Operating System). Affected by this vulnerability is some unknown functionality of the component WebKit. The manipulation with an unknown input leads to a cross-domain policy vulnerability. The CWE definition for the vulnerability is CWE-942. The product uses a cross-domain policy file that includes domains that should not be trusted. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was shared 10/25/2021 by Narendra Bhati as HT212874 as confirmed advisory (Website). The advisory is shared at support.apple.com. This vulnerability is known as CVE-2021-30887. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The advisory points out:
Processing maliciously crafted web content may lead to unexpectedly unenforced Content Security Policy
The vulnerability scanner Nessus provides a plugin with the ID 236537 (Alibaba Cloud Linux 3 : 0162: webkit2gtk3 (ALINUX3-SA-2022:0162)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 8.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
A logic issue was addressed with improved restrictions.
The vulnerability is also documented in the vulnerability database at Tenable (236537). 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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: 🔍
Exploiting
Class: Cross-domain policyCWE: CWE-942 / CWE-346 / CWE-345
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 |
Nessus ID: 236537
Nessus Name: Alibaba Cloud Linux 3 : 0162: webkit2gtk3 (ALINUX3-SA-2022:0162)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: watchOS 8.1
Timeline
04/13/2021 🔍10/25/2021 🔍
10/25/2021 🔍
10/27/2021 🔍
05/22/2025 🔍
Sources
Vendor: apple.comAdvisory: HT212874
Researcher: Narendra Bhati
Status: Confirmed
CVE: CVE-2021-30887 (🔍)
GCVE (CVE): GCVE-0-2021-30887
GCVE (VulDB): GCVE-100-185509
Entry
Created: 10/27/2021 08:36Updated: 05/22/2025 06:11
Changes: 10/27/2021 08:36 (8), 10/27/2021 08:37 (10), 10/27/2021 08:40 (28), 10/31/2021 11:52 (2), 05/22/2025 06:11 (16)
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.