dbcve.org
AndroidOperating system · Samsung

CVE-2025-20954

MEDIUM · 5.5 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 EnrichedCall prior to SMR May-2025 Release 1 allows local attackers to access sensitive information. User interaction is required for triggering this vulnerability.

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

This is an Android vulnerability in Samsung's EnrichedCall component where implicit intents are used to transmit sensitive data. Implicit intents don't specify a target component, allowing any installed app that matches the intent filter to intercept the sensitive communication. Local malicious apps can register to receive these intents and access the sensitive information. The fix requires converting implicit intents to explicit intents that specify the exact component that should handle the communication.

MitigationUpdate to SMR May-2025 Release 1 or later. For code-level remediation, convert all implicit intents used for sensitive communication to explicit intents by specifying the exact component class name, and consider adding signature-level permissions to restrict which apps can receive the intents.

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:= 13.0= 14.0= 15.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check Android version on Samsung device
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Version is 13.0, 14.0, or 15.0 (exact versions as listed in affected products)
  2. Identify if EnrichedCall component is present
    Check Samsung phone app package for EnrichedCall functionality - on Samsung devices this is typically in the Phone or Contacts app. Use ADB command 'dumpsys package | grep -i enriched' or inspect app metadata
    Affected if EnrichedCall component exists and is enabled on the device
  3. Determine if implicit intents are used for sensitive communication
    Analyze the Samsung Phone/Contacts app for implicit intent declarations in AndroidManifest.xml that handle sensitive call data. This requires decompiling the app or inspecting intent filters for actions related to EnrichedCall
    Affected if The app uses implicit intents (no explicit component specified) to transmit sensitive call information
  4. Check for malicious app intercept capability
    Verify no untrusted apps have registered intent filters that could intercept intents from the EnrichedCall component. Use ADB: 'dumpsys package' to list intent receivers, or check if any third-party apps have permission to intercept related intents
    Affected if A third-party app has an intent filter that can match and receive intents from EnrichedCall

A Samsung Android device running version 13.0, 14.0, or 15.0 with the EnrichedCall component present and using implicit intents for sensitive data transmission is vulnerable to local malicious apps intercepting that data.

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 to SMR May-2025 Release 1 or later. For code-level remediation, convert all implicit intents used for sensitive communication to explicit intents by specifying the exact component class name, and consider adding signature-level permissions to restrict which apps can receive the intents.

Recommended fix High confidence

SMR May-2025 Release 1

  1. Open Settings on the Samsung Android device
  2. Navigate to Software Update
  3. Tap Download and install to check for and apply the SMR May-2025 Release 1 update
  4. Restart the device if prompted to complete the update

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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