CVE-2023-30644
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 · uneditedStack out of bound write vulnerability in CdmaSmsParser 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 · moderate confidenceA stack-based buffer overflow vulnerability exists in the CdmaSmsParser component of RILD (Radio Interface Layer Daemon) in Samsung mobile devices running versions prior to SMR Jul-2023 Release 1. The out-of-bounds write allows attackers to overwrite stack memory and potentially execute arbitrary code.
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.
-
Confirm Samsung deviceRun 'getprop ro.product.manufacturer' or check Settings > About Phone > ManufacturerAffected if Device is not made by Samsung (this vulnerability only affects Samsung devices)
-
Verify Android versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Android version is 11.0, 12.0, or 13.0 (vulnerability only affects these versions)
-
Check Samsung SMR patch levelRun 'getprop ro.build.version.secur' to retrieve the Samsung Security Maintenance Release patch date (format: YYYY-MM-DD)Affected if SMR patch date is earlier than 2023-07-01 (the fix was released in SMR Jul-2023 Release 1)
-
Confirm RILD component presenceVerify the RILD daemon is running via 'ps -A | grep rild' or check that CdmaSmsParser functionality is available on the deviceAffected if RILD daemon is not present (the vulnerability exists within this component)
Device is affected if it is a Samsung device running Android 11.0, 12.0, or 13.0 with an SMR patch date before July 2023.
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 Jul-2023 Release 1 security patch or later, which contains the fix for this vulnerability in the RILD component.
Samsung Mobile SMR (Security Maintenance Release) Jul-2023 Release 1 or later
- Check current Android version and Samsung SMR (Security Maintenance Release) patch level on the device
- Go to Settings > Software Update on the Samsung device
- Tap 'Download and install' to check for available updates
- Apply the July 2023 SMR (SMR Jul-2023 Release 1) or later security update which contains the fix for this vulnerability
- Verify the device is now running SMR Jul-2023 Release 1 or later by checking Settings > About Phone > Software Information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30644 — 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-30644 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