LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25758: Onekey Touch devices through 4.0.0 and Onekey Mini devices through 2.10.0 allow man-in-the-middle attackers...

Onekey Touch devices through 4.0.0 and Onekey Mini devices through 2.10.0 allow man-in-the-middle attackers to obtain the seed phase. The man-in-the-middle access can only be obtained after disassembling a device (i.e., here, "man-in-the-middle" does not refer to the attacker's position on an IP network). NOTE: the vendor states that "our hardware team has updated the security patch without anyone being affected."

MediumCVSS 4.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects OneKey Touch through 4.0.0 and OneKey Mini through 2.10.0. A physically invasive man-in-the-middle setup, possible only after device disassembly, could expose the wallet seed phrase. Business risk is concentrated in custody, asset loss, and trust, not network-wide compromise.

Executive priority

Treat this as a targeted physical custody risk, not an internet-scale emergency. Prioritize asset holders, treasury operations, and any devices that left trusted control. Patch verification and tamper review are more important than broad network response.

Technical view

CVE-2023-25758 is a physical attack with high complexity and no privileges or user interaction required once device access is obtained. CVSS 3.1 is 4.2: AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N. Sources describe confidentiality impact to the seed phrase only; integrity and availability impacts are not stated.

Likely exposure

Exposure is limited to organizations or individuals using affected OneKey Touch or Mini hardware wallets, especially where devices could be stolen, intercepted, serviced, or physically tampered with. Standard network scanning will not identify this issue.

Exploitation context

The CVE explicitly says man-in-the-middle access requires device disassembly and is not an IP-network position. KEV is false, and the supplied sources do not establish active exploitation. The vendor states its hardware team updated the security patch and that no one was affected.

Researcher notes

The public record lacks detailed affected CPEs, CWEs, and independent confirmation of exploit-in-the-wild activity. Analysis should stay anchored to the stated physical-access prerequisite, affected version ranges, seed confidentiality impact, and vendor claim that a security patch was applied.

Mitigation direction

  • Identify any OneKey Touch or Mini devices in use or custody.
  • Check OneKey vendor guidance and firmware sources for the security patch status.
  • Update affected devices using vendor-supported firmware procedures.
  • Remove from service any device with suspected physical tampering.
  • Handle suspected seed exposure through the organization's wallet incident process.

Validation and detection

  • Confirm device model and firmware version against the affected version ranges.
  • Verify update status against OneKey's official firmware repository or advisory.
  • Review custody logs for loss, interception, repair, or unexplained physical access.
  • Inspect devices for signs of disassembly or tampering before reuse.
  • Document whether any affected device protected material assets.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-25758 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.2CVSS 3.1MediumCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N0.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.2Medium
CVSS 3.1 vector shape for CVE-2023-25758Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.