dbcve.org
AndroidOperating system · Samsung

CVE-2024-34593

HIGH · 8.8 CVSS v3.1 Published 2024-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Improper input validation in parsing and distributing 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 confidence

Improper input validation in the RTCP (Real-time Transport Control Protocol) packet parsing and distribution functions in librtp.so allows remote attackers to execute arbitrary code with system privileges. The vulnerability requires user interaction to trigger, suggesting the attack may involve a malicious VoIP or media session that the user must answer or initiate. The flaw was addressed in the SMR July-2024 Release 1 update.

MitigationApply the SMR July-2024 Release 1 patch or later to obtain the fixed version of librtp.so with proper RTCP input validation. Until patched, limit exposure by restricting untrusted media connections and monitoring for anomalous RTCP traffic.

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:= 12.0= 13.0= 14.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Android version
    Go to Settings > About Phone > Android version. Confirm the version is exactly 12.0, 13.0, or 14.0.
    Affected if Version is 12.0, 13.0, or 14.0 on a Samsung device and the July-2024 SMR patch has not been applied.
  2. Confirm Samsung device
    Go to Settings > About Phone > Manufacturer or Model. Verify this is a Samsung device.
    Affected if Device is not Samsung (SMR updates are Samsung-specific).
  3. Check librtp.so presence
    Using a file explorer or ADB command 'find / -name librtp.so 2>/dev/null', verify if the librtp.so library file exists on the device.
    Affected if The library is present on Samsung Android 12.0-14.0 devices without the July-2024 SMR patch.
  4. Verify SMR patch level
    Go to Settings > About Phone > Software Information > Build number. Check if the build includes the July-2024 SMR Release 1 patch or later. On Samsung, this typically appears as a date-based build (e.g., 'S9...').
    Affected if The SMR patch level is earlier than July-2024 Release 1.
  5. Assess user interaction risk
    Review installed VoIP and media applications. Check if any apps request microphone/camera permissions for calls. Identify apps that handle RTP/RTCP streams.
    Affected if The device uses untrusted VoIP or media applications that process RTCP packets without patched librtp.so.

You are affected if you have a Samsung device on Android 12.0, 13.0, or 14.0 with the librtp.so library present and the July-2024 SMR Release 1 patch has not been applied.

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 the SMR July-2024 Release 1 patch or later to obtain the fixed version of librtp.so with proper RTCP input validation. Until patched, limit exposure by restricting untrusted media connections and monitoring for anomalous RTCP traffic.

Recommended fix High confidence

SMR Jul-2024 Release 1 (July 2024 Samsung Security Update)

  1. Open Settings on the Samsung Galaxy device
  2. Navigate to Software Update
  3. Tap Download and Install to check for the July 2024 security update
  4. Ensure the device updates to SMR Jul-2024 Release 1 or later

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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