CVE-2024-25988
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 · uneditedIn SAEMM_DiscloseGuti of SAEMM_RadioMessageCodec.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 · moderate confidenceAn out-of-bounds read vulnerability exists in the SAEMM_DiscloseGuti function within SAEMM_RadioMessageCodec.c. The function fails to validate array bounds before accessing memory when processing GUTI (Globally Unique Temporary Identifier) data from radio messages, allowing an attacker to read adjacent memory contents without authentication.
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= 13.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Android version is 13.0Run 'adb shell getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version returned is exactly 13.0 (note: this CVE affects only this specific version, not later versions)
-
Identify radio/baseband firmware versionRun 'adb shell getprop gsm.version.baseband' or 'adb shell getprop ro.baseband' to retrieve the modem firmware versionAffected if The device is running Android 13.0 with a radio firmware that contains the vulnerable SAEMM_RadioMessageCodec.c code
-
Check if device uses 3GPP radio protocols with GUTI handlingThis vulnerability is in the radio protocol stack handling GUTI (Globally Unique Temporary Identifier) - typical on LTE/5G capable devices. Verify device has cellular capability via 'adb shell settings get global device_provisioned' or by checking for cellular-related servicesAffected if Device has active cellular (LTE/5G) capability and processes GUTI identifiers from network radio messages
-
Verify radio message processing is enabledThe vulnerability is triggered when processing incoming radio messages containing GUTI data. This is a passive vulnerability that triggers when the device receives specially crafted radio messages from the networkAffected if Device has cellular radio functionality enabled and can receive radio messages from network infrastructure
A device is affected if it is running exactly Android version 13.0 and uses a radio/baseband firmware containing the vulnerable SAEMM_DiscloseGuti function in SAEMM_RadioMessageCodec.c that processes GUTI data from radio messages without bounds validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper bounds checking before array access in SAEMM_DiscloseGuti to validate that the read index falls within the allocated buffer boundaries. This is a remote information disclosure vulnerability in radio protocol handling code.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25988 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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