dbcve.org
AndroidOperating system · Samsung

CVE-2024-34666

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 a specific mode 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

An out-of-bounds write vulnerability exists in librtppayload.so when parsing H.264 video format in a specific parsing mode. The vulnerability allows remote attackers to achieve arbitrary code execution with system privileges by triggering the flawed parsing logic through user interaction, such as processing a specially crafted H.264 media stream or file.

MitigationApply the SMR Oct-2024 Release 1 patch to update librtppayload.so and limit exposure by avoiding processing of untrusted H.264 media files or RTP streams until the update is applied.

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 version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 12.0, 13.0, or 14.0 (these are the affected versions)
  2. Locate librtppayload.so library
    Search for the file on the device filesystem, typically in /system/lib or /vendor/lib directories using 'find / -name librtppayload.so 2>/dev/null' via ADB
    Affected if The library exists on the device - it contains the vulnerable parsing logic for H.264 video
  3. Confirm H.264 processing capability is in use
    Identify if the device processes H.264 video streams or files through RTP, media playback, or video conferencing applications that may invoke this library
    Affected if The device processes H.264 media content (this is the trigger condition for the vulnerable code path)
  4. Check library version if extractable
    Use 'strings' or 'readelf' tools on the extracted librtppayload.so to examine build timestamps or version strings if available
    Affected if Library version predates the October 2024 security patch (vulnerable)

A Samsung Android device on version 12.0, 13.0, or 14.0 that processes H.264 media streams or files and contains the unpatched librtppayload.so is affected by this vulnerability.

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 Oct-2024 Release 1 patch to update librtppayload.so and limit exposure by avoiding processing of untrusted H.264 media files or RTP streams until the update is applied.

Recommended fix High confidence

SMR Oct-2024 Release 1 (or subsequent security updates)

  1. Open Settings on your Samsung device
  2. Navigate to Software Update
  3. Tap Download and Install to check for the October 2024 security patch
  4. Ensure the device is connected to Wi-Fi and charged during the update process
  5. After installation, verify the security patch level is SMR Oct-2024 Release 1 or later in Settings > About Phone > Software Information > Security patch level

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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