dbcve.org
AndroidOperating system · Samsung

CVE-2024-20899

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-02
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
Use of implicit intent for sensitive communication in RCS 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 confidence

The RCS (Rich Communication Services) function in the IMS service uses implicit Android intents to pass sensitive information between components. Implicit intents can be intercepted by any application registered to handle that intent type, allowing a malicious local app to capture sensitive communications. This is a vulnerability in Samsung's IMS service firmware.

MitigationUpdate the device to SMR (Samsung Mobile Security) July 2024 Release 1 or later, which contains the patch addressing this vulnerability. For developers building on affected Samsung IMS components, replace implicit intents with explicit intents that specify the exact target component.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify device is Samsung
    Check system settings or run 'getprop ro.product.brand' to confirm the device manufacturer is Samsung
    Affected if Device is not Samsung - this vulnerability only affects Samsung IMS firmware
  2. Confirm Android version is affected
    Check system settings > About Phone > Android version or run 'getprop ro.build.version.release'
    Affected if Version is 12.0, 13.0, or 14.0 - other versions are not affected by this specific CVE
  3. Check if RCS (Rich Communication Services) is enabled
    Open Phone app > Settings > RCS or check if the device has RCS messaging capability active; on some devices this may be found in Settings > Connections > Mobile Networks > RCS
    Affected if RCS is enabled - the vulnerability exists in the RCS function within the IMS service, and is only exploitable when RCS is active
  4. Verify IMS service is present
    Check system apps for 'IMS' service or run 'dumpsys package' to list installed packages and look for Samsung IMS-related packages
    Affected if IMS service is installed and running - the vulnerability exists specifically within Samsung's IMS service firmware

A user is affected if they are on a Samsung device running Android 12.0, 13.0, or 14.0 with RCS/IMS functionality enabled, as the implicit intent vulnerability exists in the RCS function of Samsung's IMS service.

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

Update the device to SMR (Samsung Mobile Security) July 2024 Release 1 or later, which contains the patch addressing this vulnerability. For developers building on affected Samsung IMS components, replace implicit intents with explicit intents that specify the exact target component.

Recommended fix High confidence

SMR Jul-2024 Release 1

  1. Check for system software updates on the Samsung device
  2. Navigate to Settings > Software update
  3. Download and install the SMR (Samsung Mobile Security) July 2024 Release 1 update
  4. Ensure the device is charged or connected to power during the update process
  5. Restart the device after the update is complete

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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