# CVE-2023-25758: Information disclosure in n/a

> Physical attackers can extract seed phase data from Onekey devices via hardware disassembly, compromising cryptographic material.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2023
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-3x3j-cw3j-2xvc

## What is CVE-2023-25758?

CVE-2023-25758 is a medium-severity vulnerability in n/a, published on 14 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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."

## Which versions are affected by CVE-2023-25758?

It affects 2 products.


Products: Onekey Onekey Mini Firmware, Onekey Onekey Touch Firmware.

## How do I fix CVE-2023-25758?

No fix has been published for CVE-2023-25758 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-25758 being exploited?

There is no known exploitation of CVE-2023-25758 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25758 and fix it if it is affected.

What it is: CVE-2023-25758 is a medium-severity vulnerability in n/a, published on 14 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25758 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-25758/ (Markdown: https://insights.sbomify.com/CVE-2023-25758/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25758
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25758
- OSV: https://osv.dev/vulnerability/CVE-2023-25758

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-25758/
Summaries are generated and may contain mistakes; the official description above is the record.