dbcve.org
AndroidOperating system · Samsung

CVE-2023-30688

HIGH · 7.8 CVSS v3.1 Published 2023-08-10
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
Out-of-bounds Write in MakeUiccAuthForOem 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 · moderate confidence

An out-of-bounds write vulnerability exists in the MakeUiccAuthForOem function within libsec-ril (a security-related RIL library used in Samsung mobile devices). The flaw allows a local attacker to write data beyond allocated buffer boundaries, potentially achieving arbitrary code execution. This affects Samsung devices running firmware versions prior to the SMR Aug-2023 Release 1.

MitigationApply the Samsung SMR Aug-2023 Release 1 or later firmware update to patch the libsec-ril library. Organizations should identify affected device models in their fleet and prioritize patching given the high-severity rating and local code execution capability.

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. Check the Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is 11.0, 12.0, or 13.0 - these are the affected version ranges per the CVE data
  2. Confirm the device is a Samsung product
    Check the device model in Settings > About Phone > Model number, or run 'getprop ro.product.model' via ADB shell
    Affected if The device is a Samsung model, as libsec-ril is a Samsung-specific security RIL library
  3. Check the Samsung Maintenance Release (SMR) version
    Run 'getprop ro.build.version.sem' via ADB shell, or check Settings > About Phone > Software info > Build number for the SMR date (format often shows as SMR-XXX)
    Affected if The SMR version is earlier than the August 2023 Release 1, or the SMR date is prior to Aug-2023
  4. Verify the libsec-ril library is present
    Check for the existence of libsec-ril.so in /system/lib/ or /vendor/lib/ directories via ADB shell using 'find / -name libsec-ril.so 2>/dev/null'
    Affected if The library exists on the device, confirming the vulnerable component is present

A Samsung device running Android 11.0, 12.0, or 13.0 with an SMR version earlier than Aug-2023 Release 1 is likely affected if the libsec-ril library is present.

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

Apply the Samsung SMR Aug-2023 Release 1 or later firmware update to patch the libsec-ril library. Organizations should identify affected device models in their fleet and prioritize patching given the high-severity rating and local code execution capability.

Recommended fix Moderate confidence

SMR Aug-2023 Release 1 (or later)

  1. Check your Samsung device model number in Settings > About Phone
  2. Visit security.samsungmobile.com and navigate to the security bulletins for August 2023
  3. Locate the SMR (Samsung Maintenance Release) Aug-2023 Release 1 for your specific device model
  4. Update your device to the August 2023 SMR release or later through Settings > Software Update > Download and Install
  5. Verify the update was applied by checking the Android security patch level in Settings > About Phone > Software Information
Caveat Standard Android/Samsung update risks apply - ensure backup of data before updating

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30688 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-30688 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