VulnerabilityPublished 6 Aug 2025

CVE-2025-21018: Samsung Mobile Blockchain Keystore · Out-of-bounds Read

Affects Samsung Mobile Blockchain KeystoreSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium : upgrade to 1.3.17.2 when convenient.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.3.17.2

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Samsung Mobile Blockchain Keystore to 1.3.17.2.

Affected software

Product	Affected	Fixed in
Samsung Mobile Blockchain Keystore	Affected <1.3.17.2	Fixed in 1.3.17.2

AI-suggested

If you cannot patch yet, organizations should enforce strict access controls to prevent unauthorized local privileged access, including robust endpoint protection, privilege management, and monitoring for suspicious privilege escalation activities. Employ mobile device management (MDM) solutions to enforce security policies and restrict installation of untrusted applications that could facilitate privilege escalation. Additionally, organizations should conduct regular security audits and penetration testing focused on privilege escalation vectors on mobile devices. For critical blockchain applications, consider additional encryption layers or hardware security modules (HSMs) to protect keys beyond the Blockchain Keystore. User education on the risks of rooting or jailbreaking devices, which can increase exposure to local attacks, is also essential.

Description

Out-of-bounds read in Blockchain Keystore prior to version 1.3.17.2 allows local privileged attackers to read out-of-bounds memory.

Impact

For European organizations, the impact of CVE-2025-21018 depends largely on the deployment of Samsung mobile devices utilizing the vulnerable Blockchain Keystore. Organizations involved in blockchain-based financial services, identity verification, or secure mobile transactions could face confidentiality risks if attackers gain local privileged access to devices. This could lead to exposure of cryptographic keys, potentially enabling unauthorized access to blockchain wallets or digital assets. Although exploitation requires local privileged access, insider threats or malware that escalates privileges could leverage this vulnerability to extract sensitive data. The impact on operational continuity is minimal since the vulnerability does not affect integrity or availability. However, the confidentiality breach could undermine trust in mobile blockchain solutions and result in regulatory compliance issues under GDPR if personal or financial data is exposed. The threat is more pronounced in sectors with high mobile device usage for blockchain applications, such as fintech, banking, and government digital identity programs in Europe.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

security.samsungmobile.com/serviceWeb.smsb?year=2025&month=08 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2025, 05:03 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats