dbcve.org
AndroidOperating system · Samsung

CVE-2023-42560

HIGH · 7.8 CVSS v3.1 Published 2023-12-05
Fix available
A fix is available. Upgrade to 14.0 or later.
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
Heap out-of-bounds write vulnerability in dec_mono_audb of libsavsac.so prior to SMR Dec-2023 Release 1 allows an 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

Heap-based buffer overflow (out-of-bounds write) in the dec_mono_audb function of libsavsac.so allows writing beyond allocated heap memory boundaries, enabling arbitrary code execution. The vulnerability exists in versions prior to the SMR Dec-2023 Release 1 patch.

MitigationUpdate libsavsac.so to version SMR Dec-2023 Release 1 or later to incorporate the patched library. Verify all systems using this library are restarted to load the updated binary.

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, < 14.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
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 if the device runs a Samsung Android version in the affected range
    Go to Settings > About Phone > Android version and verify the version is >= 11.0 and <= 14.0
    Affected if The Android version is between 11.0 and 14.0 inclusive (including 14.0)
  2. Locate libsavsac.so on the device
    Search for the file libsavsac.so in common library directories such as /system/lib/, /vendor/lib/, or /data/app/ using a file explorer or adb shell 'find / -name libsavsac.so 2>/dev/null'
    Affected if The library file libsavsac.so exists on the device
  3. Identify the installed version of libsavsac.so
    Run 'ls -la' on the found libsavsac.so file to check metadata, or use 'getprop ro.build.version.sem' if available, or inspect the library binary for version strings with 'strings' or 'grep' tools
    Affected if The library version cannot be determined or is earlier than the SMR Dec-2023 Release 1 patch version
  4. Verify if audio decoding functionality using the vulnerable dec_mono_audb function is in use
    Monitor process activity or audit logs for apps or services that invoke libsavsac.so for audio decoding operations, or check if any Samsung audio-related apps (Voice Recorder, Sound Alive, etc.) are installed and active
    Affected if The library is present and any Samsung audio processing features are actively used

The device is affected if it runs Samsung Android 11.0-14.0, contains libsavsac.so, and the library version is earlier than the SMR Dec-2023 Release 1 patch.

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
Upgrade available Upgrade to 14.0 or later
Fixed in 14.0
Interim mitigation

Update libsavsac.so to version SMR Dec-2023 Release 1 or later to incorporate the patched library. Verify all systems using this library are restarted to load the updated binary.

Recommended fix High confidence

SMR Dec-2023 Release 1 (December 2023 Security Update)

  1. On the Samsung device, go to Settings
  2. Scroll down and tap on Software update
  3. Tap on Download and install
  4. Wait for the December 2023 security update to download, then tap Install
  5. After installation completes, verify the patch level is December-2023 or later in Settings > About phone > Software information > Security patch level

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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