dbcve.org
AndroidOperating system · Samsung

CVE-2024-49415

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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-bound write in libsaped.so prior to SMR Dec-2024 Release 1 allows remote attackers to execute arbitrary code.

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

A critical out-of-bounds write vulnerability exists in libsaped.so, a Samsung proprietary library, affecting devices running SMR (Samsung Mobile Renderer) versions prior to the December 2024 Release 1. This memory corruption flaw allows remote attackers to execute arbitrary code without authentication, likely through malformed input processed by the library.

MitigationApply the SMR Dec-2024 Release 1 security update or later Samsung security patches to affected devices. This is a firmware-level fix that must be delivered through Samsung's standard security update channels.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The version is 12.0, 13.0, or 14.0 (versions prior to the December 2024 SMR update)
  2. Check security patch level
    Run 'getprop ro.build.version.security_patch' or check Settings > About Phone > Security patch level
    Affected if The patch level is earlier than December 2024 (the fix was released in the December 2024 SMR Release 1)
  3. Locate libsaped.so library
    Search for the library file: 'find / -name libsaped.so 2>/dev/null' or check common library directories like /vendor/lib/, /system/lib/, /system/vendor/lib/
    Affected if The library exists on the device, indicating the vulnerable component is present
  4. Verify library is accessible to apps
    Check file permissions with 'ls -la <path_to_libsaped.so>' and verify the library is not restricted to privileged/system-only access
    Affected if The library has world-readable permissions or is accessible to user-installed applications, allowing potential exploitation
  5. Confirm device is Samsung
    Run 'getprop ro.product.brand' or check Settings > About Phone > Manufacturer
    Affected if The device is a Samsung product, as this is a Samsung-specific proprietary library vulnerability

The device is affected if it is a Samsung Android device running version 12.0, 13.0, or 14.0 with a security patch level earlier than December 2024 and the libsaped.so library is present and accessible on the system.

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 Dec-2024 Release 1 security update or later Samsung security patches to affected devices. This is a firmware-level fix that must be delivered through Samsung's standard security update channels.

Recommended fix Moderate confidence

SMR Dec-2024 Release 1

  1. Check your Samsung device model and carrier for the availability of the December 2024 Samsung Security Maintenance Release (SMR)
  2. Navigate to Settings > Security and privacy > Security update on your Samsung Android device
  3. Verify the December 2024 security patch level is installed
  4. If the update is not available, check for system updates manually via Settings > Software update > Download and install
  5. Ensure the update is applied to address the libsaped.so vulnerability

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

Fix this in Android Scoped from the published advisory
  • Consultation12.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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