AndroidOperating system · Samsung

CVE-2023-30646

HIGH · 7.8 CVSS v3.1 Published 2023-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Heap out of bound write vulnerability in BroadcastSmsConfig of RILD prior to SMR Jul-2023 Release 1 allows attackers to execute arbitrary code.

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 confidence

Heap out-of-bounds write vulnerability in BroadcastSmsConfig of RILD (Radio Interface Layer Daemon) allows attackers to execute arbitrary code via specially crafted SMS messages. RILD handles telephony communications on Samsung Android devices, making this a critical privilege escalation in the baseband/telephony subsystem.

MitigationUpdate Samsung devices to SMR Jul-2023 Release 1 or later to receive the patched RILD binary via official OTA firmware update from Samsung.

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
AndroidOperating system
Affected:= 11.0= 12.0= 13.0

CVSS 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version shown is 11.0, 12.0, or 13.0 (without subsequent security patches)
  2. Verify the RILD daemon is present and running
    Run 'ps -A | grep rild' or 'getprop ro.radio.nrsa' via ADB shell to confirm the Radio Interface Layer Daemon is active
    Affected if RILD is running on the device (this confirms the vulnerable component exists)
  3. Check the Samsung SMR (Security Maintenance Release) patch level
    Go to Settings > About Phone > Software information > Build number, or run 'getprop ro.build.version.sem' via ADB shell
    Affected if The build shows a date before July 2023 or the SMR level is below Jul-2023 Release 1
  4. Confirm absence of the CVE-2023-30646 fix in RILD
    Since specific RILD binary version numbers are not publicly enumerated, compare your current Android version and patch level against the affected ranges; if both indicate an unpatched July 2023 or earlier state, the vulnerability is likely present
    Affected if Device runs Android 11/12/13 and has not received the SMR Jul-2023 update or later

A user is affected if the Samsung Android device runs version 11.0, 12.0, or 13.0 and has not received the July 2023 SMR security update containing the patched RILD binary.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Samsung devices to SMR Jul-2023 Release 1 or later to receive the patched RILD binary via official OTA firmware update from Samsung.

Recommended fix Moderate confidence

SMR Jul-2023 Release 1 or later (Samsung Maintenance Release)

  1. Identify if the device is a Samsung Android device (this vulnerability is Samsung-specific in the RILD component)
  2. Navigate to Settings > About Phone > Software Update on the Samsung device
  3. Check for and install any available updates. The target is SMR (Samsung Maintenance Release) Jul-2023 Release 1 or later
  4. After updating, verify the RILD component has been patched by confirming the software version reflects the July 2023 SMR or newer
Caveat Standard Samsung firmware update; ensure device is charged and backed up before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30646 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30646 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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