CVE-2021-25526
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 · uneditedIntent redirection vulnerability in Samsung Blockchain Wallet prior to version 1.3.02.8 allows attacker to execute privileged action.
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 confidenceAndroid intent redirection vulnerability in Samsung Blockchain Wallet where malicious apps can intercept or redirect intents containing sensitive data or authentication tokens, potentially allowing attackers to execute privileged actions like authorizing cryptocurrency transactions. The flaw exists in versions prior to 1.3.02.8.
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< 1.3.02.8CVSS 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 Blockchain Wallet is installedCheck your device for the Samsung Blockchain Wallet app. You can list installed packages using 'adb shell pm list packages | grep blockchain' or find it in your app drawer.Affected if The app is present on the device
-
Check installed application versionNavigate to Settings > Apps > Samsung Blockchain Wallet > App info, or use 'adb shell dumpsys package com.samsung.blockchainwallet' to retrieve the versionName and versionCode.Affected if Version cannot be determined or is earlier than 1.3.02.8
-
Compare version against affected rangeReview the version number obtained from the previous step. The vulnerable range is any version prior to 1.3.02.8.Affected if Installed version is less than 1.3.02.8 (e.g., 1.3.02.7, 1.3.01.5, etc.)
A user is affected if Samsung Blockchain Wallet version less than 1.3.02.8 is installed on the device.
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 · scoped1.3.02.8
Update Samsung Blockchain Wallet to version 1.3.02.8 or later. Users should ensure automatic updates are enabled and verify their installed version through the Google Play Store or Samsung Galaxy Store.
1.3.02.8
- Open the Galaxy Store or Google Play Store on your Samsung device
- Search for 'Samsung Blockchain Wallet'
- Update the app to version 1.3.02.8 or later
- Verify the update was successful by checking the app version in Settings > Apps > Samsung Blockchain Wallet
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-2021-25526 — 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-25526 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