dbcve.org
AndroidOperating system · Google

CVE-2024-32897

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 ProtocolCdmaCallWaitingIndAdapter::GetCwInfo() of protocolsmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to remote 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 · moderate confidence

An out-of-bounds read vulnerability exists in ProtocolCdmaCallWaitingIndAdapter::GetCwInfo() in protocolsmsadapter.cpp due to a missing bounds check. This could allow remote information disclosure through the CDMA call waiting indication handling in baseband firmware.

MitigationApply vendor-provided baseband firmware updates to address the missing bounds check in GetCwInfo(). Since exploitation requires baseband firmware compromise, ensure firmware integrity verification mechanisms are in place.

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

CVSS:3.1/AV:N/AC:H/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 baseband processor vendor
    Check /proc/cpuinfo or use 'getprop ro.baseband' to determine the baseband/modem processor (Qualcomm, MediaTek, etc.)
    Affected if The device uses a baseband processor with CDMA call waiting handling in protocolsmsadapter.cpp
  2. Check if CDMA capability is present
    Verify the device supports CDMA networks by checking cellular capability settings or using 'getprop ro.telephony.default_network'
    Affected if CDMA support is enabled - the vulnerable GetCwInfo() code path handles CDMA call waiting indications
  3. Confirm baseband firmware version
    Query baseband version via 'getprop gsm.version.baseband' or check modem firmware version in system settings under About Phone > Baseband version
    Affected if The installed baseband firmware version has not been patched by the vendor for CVE-2024-32897 (specific version depends on vendor)
  4. Verify CDMA Call Waiting feature state
    Check if CDMA call waiting is provisioned or active on the device through phone settings or cellular network information
    Affected if CDMA call waiting is enabled - the GetCwInfo() function is invoked when processing call waiting indications

A device is affected if it has a vulnerable baseband processor with CDMA call waiting capability and the baseband firmware has not been updated to include the bounds check fix in GetCwInfo().

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 vendor-provided baseband firmware updates to address the missing bounds check in GetCwInfo(). Since exploitation requires baseband firmware compromise, ensure firmware integrity verification mechanisms are in place.

Recommended fix Moderate confidence
  1. Check the Android Security Bulletin for the month this vulnerability was addressed (typically included in the monthly security patch level)
  2. Apply the latest Android system update from your device manufacturer that includes the security patch for this vulnerability
  3. Contact your device manufacturer or carrier for baseband/modem firmware updates, as this vulnerability is in the baseband component and may require a separate firmware update
  4. Verify the security patch level after updating: Go to Settings > About Phone > Security Patch Level and confirm it shows a date after the CVE was addressed
Caveat Baseband firmware updates may have carrier-specific requirements or limitations

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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