CVE-2024-20817
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 · uneditedOut-of-bounds Write vulnerabilities in svc1td_vld_slh of libsthmbc.so prior to SMR Feb-2024 Release 1 allows local attackers to trigger buffer overflow.
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 confidenceBuffer overflow vulnerability (out-of-bounds write) in the svc1td_vld_slh function within libsthmbc.so library on Samsung mobile devices prior to February 2024 security update. Local attackers can exploit this memory corruption vulnerability to write beyond allocated buffer boundaries, potentially achieving code execution or privilege escalation.
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= 11.0= 12.0= 13.0= 14.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 11.0, 12.0, 13.0, or 14.0 - these are the affected versions
-
Check Samsung security patch levelGo to Settings > About Phone > Software information > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Security patch level is earlier than February 2024 (should show 2024-02-01 or later for the fix)
-
Verify libsthmbc.so library presenceCheck for existence of /system/lib64/libsthmbc.so via ADB shell with 'ls -la /system/lib64/libsthmbc.so' or similar pathAffected if The library exists and the device meets the affected version and patch conditions above
A device is affected if it runs Android 11.0, 12.0, 13.0, or 14.0 AND has a security patch level earlier than February 2024.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Samsung SMR (Security Maintenance Release) February 2024 or later patch which addresses this vulnerability in libsthmbc.so. As this is a local attack vector, ensure devices are not compromised with malware granting local access.
SMR Feb-2024 Release 1 or later
- Check for system software updates on the Samsung Galaxy device: Go to Settings > Software Update > Download and install
- Ensure the device updates to SMR Feb-2024 Release 1 or later which contains the security patch for this vulnerability
- Verify the installed SMR version by going to Settings > About Phone > Software Information and checking the SMR (Samsung Maintenance Release) version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20817 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20817 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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