dbcve.org
AndroidOperating system · Google

CVE-2023-48411

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 SignalStrengthAdapter::FillGsmSignalStrength() of protocolmiscadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. 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 Android's SignalStrengthAdapter::FillGsmSignalStrength() function in protocolmiscadapter.cpp due to a missing bounds check. The flaw allows local information disclosure, though exploitation requires prior compromise of the baseband firmware. No user interaction is needed.

MitigationImplement proper bounds validation in the FillGsmSignalStrength() function to ensure array/buffer accesses stay within defined limits before reading signal strength data.

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. Confirm Android platform is in use
    Check system properties or /system/build.prop for android.os.Build.VERSION.SDK or android.os.Build.ID to verify the device runs Google Android OS
    Affected if The device runs any version of Google Android OS - all versions are affected by this vulnerability in the SignalStrengthAdapter::FillGsmSignalStrength() function
  2. Verify GSM/cellular telephony is active
    Check if the device has cellular capability by inspecting /system/build.prop for 'telephony.lteOnGsmDevice=1' or checking for presence of radio firmware in /firmware/image or /vendor/firmware
    Affected if GSM/cellular telephony is present and active, as the vulnerability exists in the FillGsmSignalStrength() function within the SignalStrengthAdapter that processes GSM signal strength data
  3. Check for baseband/proprietary firmware
    Inspect /proc/cmdline or /sys/class/firmware/uevent for baseband firmware indicators, or check /vendor/rfs/ for proprietary baseband files
    Affected if Baseband firmware is present - the CVE notes exploitation requires prior compromise of baseband firmware, meaning the attack surface exists where baseband processor code runs alongside the vulnerable Android telephony stack
  4. Identify telephony framework components
    Check for presence of the Android telephony service by examining if 'servicemanager' lists 'android.os.ISignalStrengthService' or by checking /system/framework/telephony-common.jar
    Affected if The Android telephony framework is present - the vulnerable code in SignalStrengthAdapter::FillGsmSignalStrength() within protocolmiscadapter.cpp is part of this framework

If the device runs Google Android OS with an active cellular telephony stack, the environment contains the vulnerable SignalStrengthAdapter::FillGsmSignalStrength() code path and is potentially affected - note that exploitation requires prior baseband firmware compromise per the CVE description.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper bounds validation in the FillGsmSignalStrength() function to ensure array/buffer accesses stay within defined limits before reading signal strength data.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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