dbcve.org
AndroidOperating system · Google

CVE-2024-34663

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Integer overflow in libSEF.quram.so prior to SMR Oct-2024 Release 1 allows local attackers to write out-of-bounds memory.

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

Integer overflow in libSEF.quram.so (Samsung's Security Element Framework library) allows local attackers to write out-of-bounds memory. This memory corruption vulnerability can lead to privilege escalation or code execution on affected Samsung devices running Android versions prior to the October 2024 security patch.

MitigationApply Samsung SMR (Security Maintenance Release) October 2024 Release 1 or later to affected devices. This is a vendor-supplied firmware update; no direct patching by end users is possible.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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. Verify device is a Samsung product
    Check the device manufacturer via 'getprop ro.product.manufacturer' or 'getprop ro.build.vendor.product.name' in ADB shell. This vulnerability exists in Samsung's Security Element Framework library (libSEF.quram.so) and only affects Samsung devices.
    Affected if Manufacturer is not Samsung - the vulnerable library is Samsung-specific and not present on other Android devices
  2. Confirm Android version is 12.0, 13.0, or 14.0
    Run 'getprop ro.build.version.release' in ADB shell or check Settings > About Phone > Android version. The vulnerability affects devices running these three Android versions.
    Affected if Android version is not 12.0, 13.0, or 14.0 - the CVE specifically lists these versions as affected
  3. Check security patch level
    Run 'getprop ro.build.version.security_patch' in ADB shell or check Settings > About Phone > Security patch level. Compare the date to October 2024.
    Affected if Security patch level is earlier than October 2024 or the field is empty - devices without the October 2024 SMR are still vulnerable
  4. Locate the vulnerable library (optional confirmation)
    Run 'find / -name libSEF.quram.so 2>/dev/null' in ADB shell to check if the Samsung SEF library exists on the device.
    Affected if The library file exists on the device - its presence confirms the Samsung SEF framework is installed and could be exploitable if other conditions are met

A Samsung device running Android 12.0, 13.0, or 14.0 with a security patch level earlier than October 2024 is likely affected by this integer overflow vulnerability in libSEF.quram.so.

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 Samsung SMR (Security Maintenance Release) October 2024 Release 1 or later to affected devices. This is a vendor-supplied firmware update; no direct patching by end users is possible.

Recommended fix High confidence

SMR Oct-2024 Release 1

  1. Check the current Android version on the Samsung device (Settings > About Phone > Android version)
  2. Identify the specific Samsung device model number
  3. Navigate to Settings > Software update > Download and install to check for available updates
  4. Apply the SMR Oct-2024 Release 1 security patch when available
  5. Verify the update was applied by checking 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
  • Consultation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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