CVE-2023-30687
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 · uneditedOut-of-bounds Write in RmtUimApdu of libsec-ril prior to SMR Aug-2023 Release 1 allows local attacker 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 confidenceThis is an out-of-bounds write vulnerability in the RmtUimApdu function within Samsung's libsec-ril library, which handles UIM (SIM) card communication. A local attacker can exploit improper bounds checking to write beyond allocated memory boundaries, potentially achieving arbitrary code execution with elevated privileges.
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.
-
Identify Android versionCheck system settings or use 'getprop ro.build.version.release' to determine the installed Android OS versionAffected if The version is 11.0, 12.0, or 13.0
-
Confirm Samsung deviceVerify the device manufacturer is Samsung using 'getprop ro.product.brand' or by checking device info in Settings > About PhoneAffected if The device is not a Samsung device (this vulnerability is Samsung-specific)
-
Locate libsec-ril librarySearch for the libsec-ril library file on the system (typically in /system/lib64/ or /vendor/lib64/) using 'find / -name libsec-ril* 2>/dev/null'Affected if The library exists and its version corresponds to the affected Android versions 11.0-13.0 without the Aug-2023 SMR patch
-
Check RmtUimApdu function availabilityInspect whether the RmtUimApdu function is exposed or accessible within the libsec-ril library using 'strings' or 'nm' tools on the library fileAffected if The function is present and the library version matches the affected versions
A Samsung Android device running version 11.0, 12.0, or 13.0 with an unpatched libsec-ril library containing the RmtUimApdu function is vulnerable to this out-of-bounds write flaw.
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 Aug-2023 Release 1 security update or later, which contains the patched libsec-ril library addressing the out-of-bounds write in RmtUimApdu.
SMR Aug-2023 Release 1 (August 2023 security patch level) or later
- Check your current Android security patch level in Settings > About Phone > Software Information > Security patch level
- If the security patch level is earlier than August 2023, proceed to update
- Go to Settings > Software Update > Download and install to check for available updates
- If an update is available, download and install the August 2023 SMR (Samsung Maintenance Release) 1 or later
- After installation, verify the security patch level now shows August 2023 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30687 — 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-30687 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