CVE-2025-21487
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 · uneditedInformation disclosure while decoding RTP packet received by UE from the network, when payload length mentioned is greater than the available buffer length.
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 confidenceThis is an information disclosure vulnerability in the RTP (Real-time Transport Protocol) decoder on User Equipment (UE). The vulnerability occurs when the RTP packet's payload length field specifies a length greater than the actual buffer allocated for receiving the packet. This causes an out-of-bounds read during packet decoding, potentially exposing sensitive memory contents beyond the allocated buffer.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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.
-
Identify the device chipset modelCheck the device specifications or system information to determine the Qualcomm chipset model (e.g., APQ8017, APQ8064AU, AQT1000, Fastconnect 6200, Fastconnect 6700, Snapdragon 460, Snapdragon 480 5G, or Snapdragon 480+ 5G SM4350 AC)Affected if The chipset matches any of the listed affected products (APQ8017, APQ8064AU, AQT1000, Fastconnect 6200, Fastconnect 6700, Snapdragon 460, Snapdragon 480 5G, or Snapdragon 480+ 5G SM4350 AC)
-
Verify the firmware versionRetrieve the firmware version from the device settings, system diagnostics, or by querying the baseband/modem subsystem (e.g., via AT command or diagnostic interface)Affected if The device runs any firmware version on the affected chipsets listed above (all versions are affected)
-
Confirm RTP processing is enabledCheck the device network configuration or telephony settings to determine if RTP (Real-time Transport Protocol) packet processing is active, or monitor network traffic to see if RTP packets are being receivedAffected if RTP packet decoding is enabled and the device processes incoming RTP streams from the network
If the device uses any of the affected Qualcomm chipsets (APQ8017, APQ8064AU, AQT1000, Fastconnect 6200, Fastconnect 6700, Snapdragon 460, Snapdragon 480 5G, or Snapdragon 480+ 5G SM4350 AC) and processes RTP traffic, the device is affected by this buffer over-read vulnerability.
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 bounds checking on the RTP payload length field against the actual buffer size before decoding. Reject packets where payload length exceeds available buffer space. Deploy via firmware update to affected UE devices.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21487 — 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-2025-21487 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