CVE-2021-25374
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 · uneditedAn improper authorization vulnerability in Samsung Members "samsungrewards" scheme for deeplink in versions 2.4.83.9 in Android O(8.1) and below, and 3.9.00.9 in Android P(9.0) and above allows remote attackers to access a user data related with Samsung Account.
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 confidenceAn improper authorization vulnerability exists in the Samsung Members Android application's handling of the 'samsungrewards' deep link scheme. The flaw allows remote attackers to bypass proper authorization checks and access user data associated with a Samsung Account through crafted deep links. This is a client-side mobile app vulnerability where the deep link handler fails to validate user authorization before returning sensitive account data.
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<= 2.4.83.9>= 3.9.00.9CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Members app is installedCheck the Android device for the Samsung Members application. On most devices, navigate to Settings > Apps > Apps list, or use adb command: `adb shell pm list packages | grep samsungmembers`Affected if The Samsung Members application is found on the device
-
Determine installed Samsung Members versionOpen Google Play Store app, search for Samsung Members, tap on the app, and view the version under 'App info'. Alternatively, use adb: `adb shell dumpsys package com.samsung.android.app.samsungmembers | grep versionName`Affected if The installed version matches either <= 2.4.83.9 or >= 3.9.00.9
-
Verify Samsung Account is linkedOpen Samsung Members app and navigate to the profile or account settings section. Check if a Samsung Account is signed in. On the device, you can also check: Settings > Accounts and backup > Accounts > Samsung accountAffected if A Samsung Account is actively linked to the device or within the Samsung Members app
-
Confirm deep link handler vulnerability exposureThis requires examining app behavior. Use an intent inspector or security tool to verify if the 'samsungrewards://' deep link scheme triggers without proper authorization validation. A security assessment tool that intercepts deep link handling can confirm if data is returned without session validationAffected if The deep link handler returns sensitive account data without requiring valid authorization tokens or session cookies
A user is affected if Samsung Members app is installed with a version <= 2.4.83.9 or >= 3.9.00.9, has a Samsung Account linked, and the 'samsungrewards' deep link scheme is accessible without proper authorization validation.
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.
From vendor dataUpdate Samsung Members to the latest version available from the Samsung Galaxy Store or Google Play Store. For enterprise environments, enforce mobile device management policies to ensure app updates and consider applying Samsung Knox security controls for Samsung devices.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25374 — 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-2021-25374 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