CVE-2023-30698
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 · uneditedImproper access control vulnerability in TelephonyUI prior to SMR Aug-2023 Release 1 allows local attacker to connect BLE without privilege.
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 · high confidenceImproper access control in Samsung's TelephonyUI component allows a local attacker to connect to Bluetooth Low Energy (BLE) devices without proper privileges. The vulnerability exists in versions prior to the SMR Aug-2023 security update and stems from insufficient authorization checks before allowing BLE connections.
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= 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Confirm device is a Samsung Android deviceGo to Settings > About Phone > Device name or manufacturer. Verify the manufacturer is Samsung.Affected if Device is not a Samsung Android device (this CVE only affects Samsung devices)
-
Check Android versionNavigate to Settings > About Phone > Android version. Confirm the installed Android version is 13.0.Affected if Android version is 13.0 (this is the affected version per the CVE)
-
Check Samsung security patch level (SMR version)Navigate to Settings > About Phone > Software information > Security patch level. Look for the SMR (Samsung Monthly Report) date.Affected if Security patch level is earlier than August 2023 (SMR Aug-2023 or later contains the fix)
-
Verify TelephonyUI component presenceThis check requires examining system logs or using a device diagnostics tool. In Settings > About Phone > Software information, confirm the build number includes the SMR patch date.Affected if Build does not reflect the August 2023 SMR update, indicating TelephonyUI remains unpatched
User is affected if they have a Samsung Android 13.0 device with a security patch level before August 2023, as the improper access control in TelephonyUI allowing unauthorized BLE connections has not been fixed.
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 August-2023 security update (or later) to affected Galaxy devices to remediate this improper access control issue.
SMR Aug-2023 Release 1 (Security Patch Level August 2023)
- Check your Samsung device model and current Android/Security Patch Level via Settings > About Phone > Software Information
- Navigate to Settings > Software Update
- Tap 'Download and install' to check for available updates
- Ensure the device updates to SMR Aug-2023 Release 1 or later which contains the fix for CVE-2023-30698
- Alternatively, manually verify via Settings > About Phone > Software Information that the Security Patch Level is August 2023 or newer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30698 — 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-30698 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