CVE-2023-30662
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExposure of Sensitive Information vulnerability in getChipIds in UwbAospAdapterService prior to SMR Jul-2023 Release 1 allows local attackers to access the UWB chipset Identifier.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local information disclosure vulnerability in Samsung's UwbAospAdapterService allows unprivileged local attackers to retrieve UWB chipset identifiers through the getChipIds method. The vulnerability exists in versions prior to the SMR July-2023 security update.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.0= 13.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check security patch levelGo to Settings > About Phone > Security patch level or run 'getprop ro.build.version.security_patch' in ADB shellAffected if Patch level is earlier than July 2023 (YYYY-MM-DD before 2023-07-01)
-
Confirm Android versionNavigate to Settings > About Phone > Android version or use 'getprop ro.build.version.release'Affected if Version is 12.0 or 13.0
-
Verify device is SamsungCheck Settings > About Phone > Device name or run 'getprop ro.product.brand'Affected if Device manufacturer is not Samsung
-
Confirm UWB service presenceCheck if /system/bin/uwb_service or com.samsung.android.UwbAospAdapterService exists on the device via ADBAffected if The vulnerable UwbAospAdapterService component is present on the device
Device is affected if it is a Samsung Android device running version 12.0 or 13.0 with a security patch level prior to July 2023, as the fix was released in the SMR July-2023 security update.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the Samsung SMR July-2023 Release 1 security patch which contains the fix for this vulnerability in the UwbAospAdapterService component.
SMR Jul-2023 Release 1 or later
- Check the current Android version and SMR (Samsung Maintenance Release) patch level on the Samsung device in Settings > About Phone > Software Information
- Ensure the device is updated to SMR (Security Maintenance Release) Jul-2023 Release 1 or later
- If not updated, check for system updates via Settings > Software Update > Download and install
- Apply any available updates to receive the security patch that fixes CVE-2023-30662
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data