CVE-2024-20845
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 releasing memory in 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 libsavsac.so during memory release operations, allowing a local attacker to execute arbitrary code via memory corruption.
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.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Android version displays 12.0 exactly (not 12.0.1, 12.0.2, etc.)
-
Locate libsavsac.so librarySearch for libsavsac.so on the device filesystem, typically found in /system/lib/ or /vendor/lib/ directories via ADB shell with 'find / -name libsavsac.so 2>/dev/null'Affected if The library file exists on the device
-
Confirm vulnerability scope is limited to Android 12.0This CVE specifically affects Samsung Android version 12.0 only; versions before 12.0 or after 12.0 (including 13.0, 14.0) are not listed as affectedAffected if The device runs exactly Android 12.0 and contains the libsavsac.so library
A device is affected if it runs Samsung Android version 12.0 exactly and contains the vulnerable libsavsac.so library; version 12.0.1 and later, or other Android versions, are not affected by this specific CVE.
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 Apr-2024 Release 1 or later security update to patch the vulnerable libsavsac.so library.
SMR Apr-2024 Release 1 (or later)
- Check current Samsung security patch level in Settings > About phone > Software information > Security patch level
- Ensure the device is connected to a network and check for system updates in Settings > Software update > Download and install
- Apply the Samsung Security Maintenance Release (SMR) April 2024 Update or later, which includes the fix for CVE-2024-20845
- After update completes, verify the Security patch level shows April 2024 or later in Settings > About phone > Software information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20845 — 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-20845 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