CVE-2024-34587
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 · uneditedImproper input validation in parsing application information from RTCP packet in librtp.so prior to SMR Jul-2024 Release 1 allows remote attackers to execute arbitrary code with system privilege. User interaction is required for triggering this vulnerability.
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 confidenceImproper input validation in librtp.so when parsing application information from RTCP (Real-time Transport Control Protocol) packets allows remote attackers to achieve arbitrary code execution with system privileges. User interaction is required to trigger the vulnerability, and the issue exists in versions prior to SMR Jul-2024 Release 1.
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= 12.0= 13.0= 14.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/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.
-
Verify Android version is affectedRun 'getprop ro.build.version.release' or check Settings > About Phone > Android version. The device is potentially affected if the version is 12.0, 13.0, or 14.0.Affected if Android version equals 12.0, 13.0, or 14.0
-
Check Samsung Security Maintenance Release dateRun 'getprop ro.build.version.sem' or check Settings > About Phone > Software Information > Security patch level. The format is typically SMR-XXX (e.g., SMR-Jul-2024).Affected if The SMR date is before July 2024 or the SMR property is missing entirely.
-
Confirm librtp.so is present on the deviceCheck for the existence of /system/lib64/librtp.so or /system/lib/librtp.so using a file manager or 'ls -la' command via ADB.Affected if The library exists and the device is on an affected Android version with pre-July-2024 SMR.
A device is affected if it runs Samsung Android 12.0, 13.0, or 14.0 AND has a Security Maintenance Release date earlier than July 2024.
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.
dbcve · scopedUpgrade to SMR Jul-2024 Release 1 or later which contains proper input validation fixes for RTCP packet parsing in librtp.so.
SMR Jul-2024 Release 1
- Check current Android version by going to Settings > About Phone > Android version
- Go to Settings > Software update > Download and install
- Ensure the device connects to a network and is charged
- Install the SMR Jul-2024 Release 1 update which contains the fix for CVE-2024-34587
- After installation, verify the patch level has been updated in Settings > About Phone > Software information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34587 — 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-34587 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