dbcve.org
AndroidOperating system · Google

CVE-2023-48401

MEDIUM · 5.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 →
57/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
In GetSizeOfEenlRecords of protocoladapter.cpp, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local 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 · moderate confidence

This is an out-of-bounds read vulnerability in the GetSizeOfEenlRecords function in protocoladapter.cpp caused by an incorrect bounds check. The vulnerability allows local information disclosure by reading memory outside the intended buffer boundaries without requiring additional privileges or user interaction.

MitigationCorrect the bounds check logic in GetSizeOfEenlRecords to properly validate buffer boundaries before memory access operations.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 the Android version
    Check the Android OS version installed on the device through Settings > About Phone > Android version, or by running 'getprop ro.build.version.release' in ADB shell
    Affected if The device runs any version of Android, as the vulnerability affects all versions of Google Android according to the affected products list
  2. Locate the vulnerable protocoladapter component
    Search for files named protocoladapter.cpp or protocoladapter on the system using 'find / -name "protocoladapter*" 2>/dev/null' in ADB shell or terminal emulator with root access
    Affected if The protocoladapter component exists on the device, indicating the vulnerable code may be present
  3. Verify the GetSizeOfEenlRecords function exists
    If the protocoladapter component is found, examine it for the GetSizeOfEenlRecords function using 'strings' or a hex editor tool, or grep for the function name within the binary
    Affected if The GetSizeOfEenlRecords function is found within the protocoladapter component, confirming the vulnerable code path is present on the device
  4. Confirm the affected subsystem
    Identify what protocol or service this adapter handles by examining the component context or associated services on the Android system
    Affected if The protocoladapter component handles network or communication protocols, as the vulnerability involves buffer boundary issues during memory access operations in GetSizeOfEenlRecords

A device is affected if it runs any version of Google Android and contains the protocoladapter component with the GetSizeOfEenlRecords function, as the vulnerability impacts all Android versions due to the incorrect bounds check in this function.

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

Correct the bounds check logic in GetSizeOfEenlRecords to properly validate buffer boundaries before memory access operations.

Recommended fix Moderate confidence

Latest Android security patch level (monthly releases contain cumulative fixes; check source.android.com/security/bulletin for the specific release containing CVE-2023-48401 fix)

  1. 1. Check your current Android security patch level in Settings > About Phone > Android version security patch level
  2. 2. Identify the Android Security Bulletin month/year that includes CVE-2023-48401 by searching source.android.com/security/bulletin
  3. 3. Apply the latest Android security update available for your device, which should include the fix for this vulnerability
  4. 4. If your device manufacturer no longer provides updates, consider upgrading to a device that receives regular security patches
Caveat Security updates are generally backward compatible; however, older devices may not receive patches if they have reached end-of-life support

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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