CVE-2024-20850
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 Samsung Pay prior to version 5.4.99 allows local attackers to access information of Samsung Pay.
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 · high confidenceThis vulnerability in Samsung Pay (versions prior to 5.4.99) allows a locally-installed malicious app to intercept sensitive communications due to the use of implicit Android intents. Implicit intents broadcast data to any app listening on the device, enabling a local attacker to capture sensitive payment-related information that should have been communicated via explicit, private 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< 5.4.99CVSS 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.
-
Verify Samsung Pay is installedCheck if Samsung Pay app exists on the device using Android PackageManager or device settings: Go to Settings > Apps and search for 'Samsung Pay', or run 'adb shell pm list packages | grep samsung.pay'Affected if Samsung Pay app is present on the device
-
Determine installed Samsung Pay versionOpen Samsung Pay in Settings > Apps > Samsung Pay > App info, or use ADB command: 'adb shell dumpsys package com.samsung.android.spay | grep versionName'Affected if A version number is returned showing the installed version
-
Compare version to affected rangeCompare the installed version number to 5.4.99. Samsung Pay uses a 3-digit version scheme (e.g., 5.4.00, 5.4.51, etc.)Affected if Installed version is less than 5.4.99 (for example, 5.4.00, 5.4.51, 5.4.98)
-
Confirm intent broadcasting is active (optional)Use a security tool or logcat to monitor intent broadcasts: 'adb logcat -b events | grep com.samsung.android.spay' during Samsung Pay usage. A vulnerable app would show intents broadcast with ACTION_VIEW or similar public actionsAffected if Intent broadcasts from Samsung Pay are observable by other apps on the device
The device is affected if Samsung Pay is installed and its version is earlier than 5.4.99, making it vulnerable to interception by malicious local apps through implicit intent broadcasting.
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 · scoped5.4.99
Update Samsung Pay to version 5.4.99 or later. This is a vendor-issued patch that replaces implicit intents with explicit intents for secure component-to-component communication.
5.4.99
- Open the Galaxy Store or Google Play Store on your Samsung device
- Search for Samsung Pay
- Update Samsung Pay to version 5.4.99 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20850 — 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-20850 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