dbcve.org
AndroidOperating system · Google

CVE-2023-48410

HIGH · 7.5 CVSS v3.1 Published 2023-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
In cd_ParseMsg of cd_codec.c, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

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

An out-of-bounds read vulnerability exists in the cd_ParseMsg function in cd_codec.c due to a missing bounds check. This allows remote attackers to read memory contents beyond intended buffer boundaries, leading to information disclosure without requiring any user interaction or elevated privileges.

MitigationImplement proper bounds validation before reading data in cd_ParseMsg to ensure all buffer accesses stay within allocated memory regions.

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:all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify cd codec library presence
    Locate the cd_codec library or libcd library on the Android system, typically found in /system/lib/ or /vendor/lib/ directories. Use 'find /system -name *cd*codec*' or 'find /vendor -name *cd*codec*' to locate relevant shared objects (.so files).
    Affected if The cd_codec library (cd_codec.c component) is present on the device, as this indicates the vulnerable code exists in the environment.
  2. Determine library version
    Check the version metadata of the identified cd codec library using 'getprop ro.build.version.sdk' to get Android version, and examine the library file details with 'ls -la' or use 'strings' on the .so file to find version strings. Compare against any available version information from Android security bulletins.
    Affected if Any version of the cd codec library is installed, as the vulnerability affects all versions of Android according to the provided scope.
  3. Verify cd_ParseMsg function exposure
    Check if the cd codec is accessible to applications by examining whether the library is loaded by any running processes. Use 'adb shell ps -A | grep -i <package>' to see if apps using the codec are running, or check /proc/<pid>/maps for processes that have loaded libcd or cd_codec.
    Affected if The cd_ParseMsg function is in a library that can be invoked by any application, as the vulnerability requires no user interaction or privileges to trigger.
  4. Confirm network-exposed attack surface
    Determine if the device processes cd codec data from untrusted network sources. Check if any apps or services handle cd-format media streams from network connections. Examine network listening services with 'netstat -tulpn' or check app permissions for network access.
    Affected if The device processes cd codec data from network sources, as remote attackers can exploit this without user interaction.

If the cd_codec component exists on an Android device and processes data from any source, the environment is affected by this out-of-bounds read vulnerability in cd_ParseMsg.

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

Implement proper bounds validation before reading data in cd_ParseMsg to ensure all buffer accesses stay within allocated memory regions.

Recommended fix High confidence

December 2023 Android Security Patch Level or later

  1. Check the Android Security Bulletin for the month this CVE was addressed (CVE-2023-48410 was addressed in the December 2023 Android Security Bulletin)
  2. Apply the latest Android security patch update for your device. Go to Settings > System > Security update > Security patch level
  3. Ensure your device has the December 2023 security patch level or later installed

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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