dbcve.org
AndroidOperating system · Samsung

CVE-2023-30739

HIGH · 7.8 CVSS v3.1 Published 2023-11-07
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
Arbitrary File Descriptor Write vulnerability in libsec-ril prior to SMR Nov-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 confidence

This is an arbitrary file descriptor write vulnerability in Samsung's libsec-ril library (part of the Radio Interface Layer security components) that allows a local attacker to execute arbitrary code. The flaw exists in versions prior to the SMR November-2023 Release 1 security patch. By writing to arbitrary file descriptors, an attacker could potentially gain elevated privileges or execute malicious code in the context of the vulnerable service.

MitigationApply the Samsung SMR November-2023 Release 1 or later security patch to affected devices, as Samsung provides the fix through their official firmware update mechanism.

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. Confirm device is a Samsung Android phone
    Check the device manufacturer and model via Settings > About Phone or by running 'getprop ro.product.manufacturer' and 'getprop ro.product.model' in ADB shell
    Affected if Manufacturer is not Samsung - the vulnerability is specific to Samsung devices only
  2. Identify the Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in ADB shell
    Affected if Version is 11.0, 12.0, or 13.0 - versions outside this range are not affected
  3. Check the security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' in ADB shell
    Affected if Patch level is earlier than 2023-11-01 - devices without the November 2023 security update are vulnerable if they run the affected Android versions
  4. Verify the libsec-ril library presence
    Check for the existence of libsec-ril library in the system partition via 'ls /system/lib/libsec-ril*' or '/vendor/lib/libsec-ril*' in ADB shell
    Affected if The library exists on the device - the vulnerability resides in this component

A Samsung Android device running version 11.0, 12.0, or 13.0 with a security patch level before November 2023 is affected by this vulnerability.

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 November-2023 Release 1 or later security patch to affected devices, as Samsung provides the fix through their official firmware update mechanism.

Recommended fix High confidence

SMR Nov-2023 Release 1 (Samsung Monthly Security Patch)

  1. Check the current Android security patch level on the device (Settings > About Phone > Software Information > Security patch level)
  2. Verify if the device has received the SMR Nov-2023 Release 1 update from Samsung. Go to Settings > Software Update > Download and install
  3. If the update is not available, check with the device carrier or Samsung support for update availability
  4. Apply the November 2023 Samsung Security Update (SMR Nov-2023 Release 1) which contains the fix for CVE-2023-30739 in libsec-ril
  5. After updating, verify the security patch level shows November 2023 or later
Caveat Samsung security updates are cumulative; applying this patch should not introduce breaking changes as it is a routine monthly security update

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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