CVE-2023-30649
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 · uneditedHeap out of bound write vulnerability in RmtUimNeedApdu 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 confidenceHeap-based buffer overflow in RILD's RmtUimNeedApdu function, which handles SIM/USIM card APDU communication. The out-of-bounds write allows attackers to achieve arbitrary code execution in the context of the RILD daemon, a privileged system service.
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= 11.0= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 11.0, 12.0, or 13.0 on a Samsung device
-
Verify device is SamsungRun 'getprop ro.product.brand' or 'getprop ro.manufacturer' via ADBAffected if Brand is Samsung or manufacturer is Samsung Electronics
-
Confirm RILD is runningRun 'ps -A | grep rild' via ADB shell to check if the RILD process is activeAffected if RILD daemon is running (this is required for the vulnerable code path to be present)
-
Check SIM/USIM card is activeRun 'service list' or check Settings > Connections > SIM card manager to verify SIM functionality is enabledAffected if A SIM or USIM card is inserted and actively communicating with RILD (the vulnerable RmtUimNeedApdu function handles this communication)
If running Samsung Android 11.0, 12.0, or 13.0 with an active SIM/USIM card and the RILD daemon running, the environment is affected by this vulnerability in the RmtUimNeedApdu function.
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 · scopedUpdate device firmware to SMR Jul-2023 Release 1 or later, as this version contains the patched RILD with proper bounds checking in the RmtUimNeedApdu function.
SMR Jul-2023 Release 1 or later (Samsung Maintenance Release)
- 1. Identify the Samsung device model affected
- 2. Check if the device is eligible for Samsung's July 2023 security update (SMR Jul-2023 Release 1 or later)
- 3. Navigate to Settings > Security & privacy > Security update on the Samsung device
- 4. Check the current Security patch level in the device settings
- 5. If the Security patch level is earlier than July 2023, download and install any available system updates
- 6. Alternatively, manually flash the latest firmware containing SMR Jul-2023 or later via Samsung's firmware download tools ( Odin or Smart Switch )
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30649 — 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-30649 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