| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Apple watchOS up to 9.3.1. This affects an unknown function of the component Kernel. Executing a manipulation can lead to memory corruption. This vulnerability is handled as CVE-2023-27933. It is possible to launch the attack on the local host. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Apple watchOS up to 9.3.1 (Smartwatch Operating System). It has been declared as critical. This vulnerability affects an unknown functionality of the component Kernel. 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. CVE summarizes:
The issue was addressed with improved memory handling. This issue is fixed in macOS Ventura 13.3, iOS 16.4 and iPadOS 16.4, macOS Monterey 12.6.4, tvOS 16.4, watchOS 9.4. An app with root privileges may be able to execute arbitrary code with kernel privileges.
The weakness was released 03/27/2023 by sqrtpwn as HT213678 as confirmed advisory (Website). The advisory is available at support.apple.com. This vulnerability was named CVE-2023-27933. The technical details are unknown and an exploit is not available. The advisory points out:
An app with root privileges may be able to execute arbitrary code with kernel privileges
Upgrading to version 9.4 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
The issue was addressed with improved memory handling.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-31659). If you want to get best quality of vulnerability data, you may have to visit 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.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.7
NVD Vector: 🔍
CNA Base Score: 6.7
CNA 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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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 9.4
Timeline
03/08/2023 🔍03/27/2023 🔍
03/27/2023 🔍
03/29/2023 🔍
11/28/2025 🔍
Sources
Vendor: apple.comAdvisory: HT213678
Researcher: sqrtpwn
Status: Confirmed
CVE: CVE-2023-27933 (🔍)
GCVE (CVE): GCVE-0-2023-27933
GCVE (VulDB): GCVE-100-224386
EUVD: 🔍
Entry
Created: 03/29/2023 14:49Updated: 11/28/2025 14:52
Changes: 03/29/2023 14:49 (19), 03/29/2023 14:52 (27), 04/19/2023 09:33 (1), 01/30/2025 10:19 (35), 11/28/2025 14:52 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.

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