dbcve.org
AndroidOperating system · Samsung

CVE-2023-52432

HIGH · 7.1 CVSS v3.1 Published 2024-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
Improper input validation in IpcTxSndSetLoopbackCtrl in libsec-ril prior to SMR Sep-2023 Release 1 allows local attackers to write out-of-bounds memory.

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

Improper input validation in the IpcTxSndSetLoopbackCtrl function within Samsung's libsec-ril library allows a local attacker to write data beyond allocated memory boundaries. This memory corruption vulnerability stems from insufficient validation of input parameters before performing a write operation, potentially enabling arbitrary code execution or privilege escalation on affected Samsung mobile devices running Android with the vulnerable sec-ril component.

MitigationApply the Samsung SMR September-2023 Release 1 or later security update to obtain the patched libsec-ril library; this is a firmware-level update that cannot be addressed through application-level patches.

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:= 13.0= 14.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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 Samsung Android
    Check device manufacturer and model via Settings > About Phone, or run 'getprop ro.product.manufacturer' and 'getprop ro.product.model' via adb
    Affected if Device is not Samsung Android (the vulnerability is specific to Samsung's libsec-ril)
  2. Check Android version
    Go to Settings > About Phone > Software Information > Android version, or run 'getprop ro.build.version.release' via adb
    Affected if Android version is 13.0 or 14.0 (these are the only affected versions listed)
  3. Verify Samsung security patch level
    Go to Settings > About Phone > Software Information > Security patch level, or run 'getprop ro.build.version.security_patch' via adb
    Affected if Security patch level is earlier than September 2023 (the patch was released in Samsung SMR September-2023 Release 1)
  4. Check sec-ril component presence
    Run 'pm list packages | grep -i ril' via adb to list RIL-related packages, or check /system/lib/libsec-ril.so if accessible
    Affected if The sec-ril component exists on the device (the vulnerability resides in libsec-ril library)
  5. Identify RIL daemon status
    Run 'ps -A | grep -i rild' via adb to check if the RIL daemon is running
    Affected if The rild process is active (the vulnerable code path executes when RIL is operational)

A Samsung Android device running version 13.0 or 14.0 with a security patch level before September 2023 has the vulnerable libsec-ril component exposed to the memory corruption flaw in IpcTxSndSetLoopbackCtrl.

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 September-2023 Release 1 or later security update to obtain the patched libsec-ril library; this is a firmware-level update that cannot be addressed through application-level patches.

Recommended fix High confidence

Samsung SMR Sep-2023 Release 1 (September 2023 Security Patch Level)

  1. Check for system updates on the Samsung Android device by navigating to Settings > Software Update > Download and install
  2. Ensure the device receives the Samsung Security Maintenance Release (SMR) Sep-2023 Release 1 or later update
  3. Verify the update was applied by checking Settings > About Phone > Software Information and confirming the Security patch level is September 2023 or later
  4. If OTA update is not available, contact the device carrier or Samsung support for firmware update delivery

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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