CVE-2025-21017
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 detaching crypto box 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 'detaching crypto box' function of Blockchain Keystore versions prior to 1.3.17.2. Local privileged attackers can exploit this memory corruption flaw to write data beyond allocated buffer boundaries, potentially achieving code execution or causing 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.
-
Confirm Blockchain Keystore is installedLocate the Samsung Blockchain Keystore application on the device. This is typically found in the device settings under 'Security and Privacy' or as a system app component on Samsung devices supporting blockchain features. Check the application's package name or app info.Affected if The application or component is present on the device
-
Identify the installed versionAccess the app information page for Blockchain Keystore (usually via Settings > Apps > Blockchain Keystore or Settings > Security and Privacy > Blockchain Keystore > About) and record the version number displayed.Affected if Version number cannot be determined or is not visible
-
Compare version against vulnerable rangeTake the installed version number (for example, 1.3.17.1, 1.3.16.0, etc.) and compare it numerically to 1.3.17.2. The first two numbers (1.3) must match; then compare the third number (17) and fourth number (2) to determine if the installed version is lower.Affected if Installed version is less than 1.3.17.2 (for example, 1.3.17.1, 1.3.16.5, 1.3.15.0, etc.)
The device is affected if Samsung Blockchain Keystore is installed and its version number is lower than 1.3.17.2.
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
Upgrade Blockchain Keystore to version 1.3.17.2 or later to remediate this vulnerability.
1.3.17.2
- Open device Settings and navigate to Apps or Apps & notifications
- Locate and tap on Blockchain Keystore in the app list
- Tap on App info or view the app details
- Check the current version under App version or Version info
- Update the app to version 1.3.17.2 or later via the Galaxy Store, Google Play Store, or Samsung system update if available
- Alternatively, ensure the device has the latest Samsung software updates installed which may include the Blockchain Keystore fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21017 — 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-21017 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