CVE-2024-20846
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 vulnerability while decoding hcr of libsavsac.so prior to SMR Apr-2024 Release 1 allows local attacker 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 confidenceAn out-of-bounds write vulnerability exists in the libsavsac.so library when decoding hcr data, allowing a local attacker to write beyond allocated buffer boundaries and achieve arbitrary code execution. The vulnerability stems from insufficient bounds checking during the hcr decoding process in the library.
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= 12.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.
-
Verify Android version is 12.0Check the system build properties using 'getprop ro.build.version.release' or view Android version in Settings > About PhoneAffected if The device is running Android 12.0 exactly (version 12.0) as listed in the affected versions
-
Locate the libsavsac.so library on the deviceSearch for the library file in system directories, typically found under /system/lib/ or /system/lib64/Affected if The library file exists on the device - this library contains the vulnerable hcr decoding component
-
Check the installed version of libsavsac.soUse 'ls -la' on the library file to view its metadata, or use a file analysis tool to extract version strings from the binaryAffected if The library version is older than the SMR Apr-2024 Release 1 patch version which contains proper bounds validation
-
Identify if hcr decoding functionality is in useMonitor for processes or services that utilize the libsavsac.so library, or check Samsung backup/security application logs for hcr-related operationsAffected if Any Samsung application or service is actively decoding hcr data using the vulnerable library
A device is affected if it runs Android 12.0 and contains the vulnerable libsavsac.so library version prior to the Apr-2024 security patch.
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 the SMR Apr-2024 Release 1 or later patch to update the libsavsac.so library to a version with proper bounds validation during hcr decoding.
Samsung SMR Apr-2024 Release 1 (April 2024 Security Patch Level)
- Check for system updates on the Samsung device and install any available updates
- Navigate to Settings > Security and privacy > Security update on Samsung Android device
- Ensure the device is updated to the April 2024 Security Maintenance Release (SMR) or later
- Verify the installed security patch level is April 2024 or higher in Settings > About phone > Software information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20846 — 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-20846 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