Google Pixel Watch 11 DeviceVersionFragment.java checkDebuggingDisallowed privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Google Pixel Watch 11. The impacted element is the function checkDebuggingDisallowed of the file DeviceVersionFragment.java. The manipulation results in privileges management.
This vulnerability is cataloged as CVE-2023-48418. The attack may be launched remotely. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as very critical, was found in Google Pixel Watch 11. Affected is the function checkDebuggingDisallowed of the file DeviceVersionFragment.java. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was shared 01/03/2024. The advisory is shared for download at source.android.com. This vulnerability is traded as CVE-2023-48418 since 11/16/2023. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 01/23/2024). The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.2VulDB Meta Temp Score: 9.1
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 10.0
CNA Vector (Google Devices): 🔍
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: 🔍
0-Day Time: 🔍
Timeline
11/16/2023 🔍01/03/2024 🔍
01/03/2024 🔍
01/23/2024 🔍
Sources
Vendor: google.comAdvisory: 176446
Status: Confirmed
CVE: CVE-2023-48418 (🔍)
GCVE (CVE): GCVE-0-2023-48418
GCVE (VulDB): GCVE-100-249564
Entry
Created: 01/03/2024 09:25Updated: 01/23/2024 10:37
Changes: 01/03/2024 09:25 (48), 01/23/2024 10:32 (2), 01/23/2024 10:37 (12)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.