CVE-2025-21021
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 · uneditedOut-of-bounds write in drawing pinpad in Blockchain Keystore prior to version 1.3.17.2 allows local privileged attackers to write out-of-bounds memory.
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 out-of-bounds write vulnerability exists in the pinpad drawing functionality of the Blockchain Keystore application. The vulnerability allows a local privileged attacker to write data beyond allocated memory boundaries, which could potentially be exploited to achieve code execution or cause a denial of service.
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.17.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Check if Samsung Blockchain Keystore is installedOn a Samsung device, go to Settings > Apps > Samsung Blockchain Keystore, or use ADB command: 'adb shell pm list packages | grep blockchain'Affected if The package com.samsung.android.knox.keychain or similar Samsung Blockchain Keystore package is found on the device
-
Determine the installed version of Samsung Blockchain KeystoreIn Settings > Apps > Samsung Blockchain Keystore > App info, note the version number displayed. Alternatively, use ADB: 'adb shell dumpsys package com.samsung.android.knox.keychain | grep versionName'Affected if A version number is displayed that is lower than 1.3.17.2
-
Verify the vulnerability applies to your use caseConfirm the pinpad drawing feature is enabled or accessible. This feature is typically used during wallet setup or authentication within the Blockchain Keystore application.Affected if The pinpad drawing functionality is present and used on the device, and the version is below 1.3.17.2
You are affected if Samsung Blockchain Keystore is installed with a version lower than 1.3.17.2 and the pinpad drawing feature is in use.
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.17.2
Update Blockchain Keystore to version 1.3.17.2 or later to obtain the patch for this vulnerability. Since the attack requires local privileged access, ensure strict access controls on systems running this software.
1.3.17.2 or later
- Check the current version of Blockchain Keystore on the device
- Upgrade Blockchain Keystore to version 1.3.17.2 or later through the Samsung Galaxy Store or system software update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21021 — 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-2025-21021 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