CVE-2024-20897
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 · uneditedUse of implicit intent for sensitive communication in FCM function in IMS service prior to SMR Jul-2024 Release 1 allows local attackers to get sensitive information.
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 confidenceThis vulnerability in Samsung's IMS service prior to the July 2024 SMR release uses implicit intents (Android IPC mechanism) for sensitive Firebase Cloud Messaging (FCM) communications. Implicit intents can be intercepted by any local application, allowing an attacker with local device access to capture sensitive information transmitted through these improperly secured communication 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= 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Android version on the Samsung deviceGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The device runs Android 12.0, 13.0, or 14.0
-
Check Samsung SMR (Security Maintenance Release) dateGo to Settings > About Phone > Software information > SMR (Security Maintenance Release), or run 'getprop ro.build.version.smr' via ADBAffected if The SMR date is before July 2024 (the patch release date)
-
Verify IMS service is present on the deviceCheck for the IMS-related package via ADB command: 'adb shell pm list packages | grep -i ims' or inspect running processes with 'adb shell ps -A | grep -i ims'Affected if The IMS service is installed and running on the device
A Samsung Android device running version 12.0, 13.0, or 14.0 with a July 2024 SMR date earlier than the patch release is likely affected by this vulnerability in the IMS service.
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 · scopedReplace implicit intents with explicit intents in the FCM function of the IMS service, specifying the exact target component to prevent unauthorized interception by other applications.
SMR Jul-2024 Release 1 or later
- Navigate to Settings > Software Update on the Samsung device
- Tap 'Download and install' to check for available updates
- Locate and install the SMR July-2024 Release 1 update (or later) which includes the security patch for CVE-2024-20897
- Verify the update was installed by checking Settings > About Phone > Software Information and confirming the Security patch level is July 2024 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20897 — 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-20897 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