dbcve.org
Samsung Blockchain KeystoreApplication · Samsung

CVE-2023-21506

HIGH · 7.8 CVSS v3.1 Published 2023-05-04
Fix available
A fix is available. Upgrade to 1.3.12.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Out-of-bounds Write vulnerability while processing BC_TUI_CMD_SEND_RESOURCE_DATA_ARRAY command in bc_tui trustlet from Samsung Blockchain Keystore prior to version 1.3.12.1 allows local attacker to execute arbitrary code.

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 confidence

An out-of-bounds write vulnerability exists in the bc_tui trustlet of Samsung Blockchain Keystore when processing the BC_TUI_CMD_SEND_RESOURCE_DATA_ARRAY command. This allows a local attacker to write data beyond allocated buffer boundaries and potentially execute arbitrary code in the trusted execution environment.

MitigationUpdate Samsung Blockchain Keystore to version 1.3.12.1 or later to patch the vulnerability. As this is a TEE component, the update would come through Samsung's regular firmware/software update mechanism.

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
Samsung Blockchain KeystoreApplication
Affected:< 1.3.12.1

CVSS 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Samsung Blockchain Keystore is installed
    On the Samsung device, go to Settings > Apps and search for 'Blockchain Keystore', or run 'adb shell pm list packages | grep -i blockchain' to list installed packages related to blockchain.
    Affected if The Samsung Blockchain Keystore application is present on the device.
  2. Determine the installed version of Samsung Blockchain Keystore
    In Settings > Apps > Blockchain Keystore > App info, note the version number displayed under the app name. Alternatively, run 'adb shell dumpsys package <package_name> | grep versionName' where package_name is the Blockchain Keystore package.
    Affected if The displayed version number is lower than 1.3.12.1.
  3. Confirm the bc_tui trustlet component exists
    The bc_tui trustlet is a TEE component within Samsung Blockchain Keystore. Its presence is implied by the app installation. There is no direct user-accessible way to enumerate TEE trustlets from the Android UI; the trustlet ships as part of the Blockchain Keystore package.
    Affected if Samsung Blockchain Keystore is installed, indicating the bc_tui trustlet is present.
  4. Check device firmware and security patch level
    Review the device's Android security patch level in Settings > About phone > Software information > Security patch level. TEE components like trustlets are updated through Samsung firmware updates.
    Affected if The device is running firmware that does not include the updated Samsung Blockchain Keystore version 1.3.12.1 or later.

A user is affected if Samsung Blockchain Keystore is installed and its version is below 1.3.12.1, as the vulnerable bc_tui trustlet is present in unpatched versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3.12.1 or later
Fixed in 1.3.12.1
Interim mitigation

Update Samsung Blockchain Keystore to version 1.3.12.1 or later to patch the vulnerability. As this is a TEE component, the update would come through Samsung's regular firmware/software update mechanism.

Recommended fix High confidence

1.3.12.1

  1. 1. Verify the current version of Samsung Blockchain Keystore installed on the device
  2. 2. Open Galaxy Store or the device's app store
  3. 3. Search for Samsung Blockchain Keystore
  4. 4. Update the application to version 1.3.12.1 or later
  5. 5. Alternatively, check for system software updates as the fix may be included in Samsung's security patch releases

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Samsung Blockchain Keystore Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-21506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-21506 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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