dbcve.org
AndroidOperating system · Samsung

CVE-2023-21476

HIGH · 7.8 CVSS v3.1 Published 2025-09-03
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 vulnerability in libaudiosaplus_sec.so library prior to SMR Apr-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 in the libaudiosaplus_sec.so library allows a local attacker to write beyond allocated memory boundaries and execute arbitrary code with elevated privileges.

MitigationApply the Samsung SMR April 2023 security update or later, which includes the patched libaudiosaplus_sec.so library.

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 Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version equals 11.0, 12.0, or 13.0
  2. Verify libaudiosaplus_sec.so exists
    Check if the file /vendor/lib64/libaudiosaplus_sec.so or /system/lib64/libaudiosaplus_sec.so exists using 'ls -la' via ADB shell or a file manager with root access
    Affected if The library file exists on the device
  3. Confirm library is in use
    Run 'ps -A | grep audiosaplus' or check /proc/<pid>/maps for any process loading libaudiosaplus_sec.so
    Affected if The library is loaded into memory by any running process

The device is affected if it runs Android 11.0, 12.0, or 13.0 AND contains the libaudiosaplus_sec.so library, as the vulnerability exists in this specific library on those versions.

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 April 2023 security update or later, which includes the patched libaudiosaplus_sec.so library.

Recommended fix High confidence

Samsung SMR (Security Maintenance Release) Apr-2023 or later for Android 11, 12, and 13

  1. Check if your Samsung device is receiving monthly security updates from your carrier or Samsung
  2. Navigate to Settings > Security and privacy > Security update on your Samsung Android device
  3. Verify the Samsung Security Maintenance Release (SMR) date is April 2023 or later
  4. If available, tap 'Download and install' to apply the latest security patch
  5. Alternatively, check for system updates via Settings > Software update > Download and install
  6. After updating, verify the patch is applied by returning to Settings > Security and privacy > Security update and confirming the date
Caveat Standard security update risks - updates are generally low-risk but ensure device is charged and backed up before applying

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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