CVE-2024-34589
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 RTCP RR packet in librtp.so prior to SMR Jul-2024 Release 1 allows remote attackers to trigger temporary denial of service. 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 confidenceA vulnerability in librtp.so allows remote attackers to cause a denial of service via improper input validation when parsing malformed RTCP (Real-time Transport Control Protocol) Receiver Report (RR) packets. The parsing code fails to properly validate the structure or content of RTCP RR packets before processing, leading to a crash or hang condition.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 affectedGo to Settings > About Phone > Android version and confirm it shows 12.0, 13.0, or 14.0Affected if Android version is 12.0, 13.0, or 14.0 on a Samsung device
-
Confirm librtp.so is presentCheck for the existence of /system/lib/librtp.so or /system/lib64/librtp.so using a file manager or ADB shell with 'ls -la'Affected if librtp.so exists in system libraries (it is present by default on affected versions)
-
Identify apps using RTP/RTCP functionalityReview installed apps for those that handle real-time audio/video communication such as VoIP clients, video conferencing apps, or video calling features in messaging appsAffected if Any app using RTP/RTCP protocols for real-time media transmission is installed and active
User is affected if running Samsung Android 12.0, 13.0, or 14.0 with librtp.so present and any RTP/RTCP-enabled application in use that can receive malformed RTCP RR packets.
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 · scopedUpdate librtp.so to the SMR Jul-2024 Release 1 or later version which contains the fix for proper input validation in RTCP RR packet parsing. Verify that RTP/RTCP functionality continues to work correctly after the update.
SMR Jul-2024 Release 1
- Check your Samsung device model for SMR Jul-2024 Release 1 availability via security.samsungmobile.com
- Navigate to Settings > Software Update on your Samsung Android device
- Download and install the July 2024 security patch update (SMR Jul-2024 Release 1)
- Restart the device to complete the update process
- Verify the patch is installed by checking Settings > Software Update > Samsung security update level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34589 — 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-34589 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