dbcve.org
AndroidOperating system · Samsung

CVE-2024-34665

HIGH · 8.8 CVSS v3.1 Published 2024-10-08
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
Out-of-bounds write in parsing h.264 format in librtppayload.so prior to SMR Oct-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 · high confidence

Out-of-bounds write vulnerability in the h.264 video parsing code of librtppayload.so allows remote attackers to write beyond allocated buffer boundaries when processing malicious h.264 streams, potentially achieving arbitrary code execution with system privileges. User interaction is required to trigger the vulnerability, likely through a crafted media file or stream.

MitigationUpgrade to SMR Oct-2024 Release 1 or later which contains the patched librtppayload.so. If immediate patching is not possible, restrict media input processing and validate h.264 stream sources before ingestion.

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. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is 12.0, 13.0, or 14.0 (the only affected versions)
  2. Locate librtppayload.so library
    Search for the file using 'find / -name librttpayload.so 2>/dev/null' via ADB shell or examine system libs in /system/lib64 or /vendor/lib64
    Affected if The library exists on the device, indicating the vulnerable component is present
  3. Check for media/RTP processing functionality
    Identify if any applications or services on the device process RTP streams or h.264 video (e.g., video conferencing apps, streaming clients, VoIP tools)
    Affected if Apps that process h.264 streams via RTP are installed and used, enabling the attack surface
  4. Verify media input processing is accessible
    Review which apps have permission to access media streams and whether unknown or untrusted sources can submit media content to the device
    Affected if The device accepts h.264 media input from external or untrusted sources without validation
  5. Assess user interaction exposure
    Determine if users on the device are likely to open crafted media files or connect to untrusted media streams
    Affected if Users may open media files from untrusted sources or connect to suspicious RTP streams, satisfying the user interaction requirement

The device is affected if it runs Android 12.0, 13.0, or 14.0 and contains the vulnerable librtppayload.so library with media processing capabilities exposed to user-supplied h.264 content.

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

Upgrade to SMR Oct-2024 Release 1 or later which contains the patched librtppayload.so. If immediate patching is not possible, restrict media input processing and validate h.264 stream sources before ingestion.

Recommended fix Moderate confidence

SMR Oct-2024 Release 1 (October 2024 security patch level)

  1. Check for system software updates on your Samsung Galaxy device and install the October 2024 security update (SMR Oct-2024 Release 1) or later
  2. Navigate to Settings > Software update > Download and install
  3. After updating, verify the device is running the October 2024 SMR or later by checking Settings > About phone > Software information > Build number

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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