UWB chipset identifier disclosure via missing permission check
Published Jul 6, 2023 · Updated Oct 31, 2024
Information disclosure in Samsung Mobile Devices on Android 12 and 13 allows local users to read the UWB chipset identifier. The getChipIds method in UwbAospAdapterService returns the identifier without enforcing the permission added by the patch. A locally executing caller can obtain the hardware identifier without privileges or user interaction; no integrity or availability impact is reported.
Summary
What happened
Information disclosure in Samsung Mobile Devices on Android 12 and 13 allows local users to read the UWB chipset identifier. The getChipIds method in UwbAospAdapterService returns the identifier without enforcing the permission added by the patch. A locally executing caller can obtain the hardware identifier without privileges or user interaction; no integrity or availability impact is reported.
The record
- CVE
- CVE-2023-30662
- Published
- Jul 6, 2023
- Updated
- Oct 31, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 6, 2023CVE publishedPublication date reported by the CVE source.
- Oct 31, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo