CVE-2025-69893
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2025-69893 is a medium-severity Covert Timing Channel (CWE-385) vulnerability in Trezor One (inferred from references). Its CVSS base score is 4.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as Other Platforms; in the Adversarial Attacks risk domain.
The strongest mitigations our analysis identified map to SC-31 (Covert Channel Analysis) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-209448
Vulnerability Data
A side-channel vulnerability exists in the implementation of BIP-39 mnemonic processing, as observed in Trezor One v1.13.0 to v1.14.0, Trezor T v1.13.0 to v1.14.0, and Trezor Safe v1.13.0 to v1.14.0 hardware wallets. This originates from the BIP-39 standard guidelines, which…
more
induce non-constant time execution and specific branch patterns for word searching. An attacker with physical access during the initial setup phase can collect a single side-channel trace. By utilizing profiling-based Deep Learning Side-Channel Analysis (DL-SCA), the attacker can recover the mnemonic code and subsequently steal the assets. The issue was patched.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Other Platforms
- Risk Domain
- Adversarial Attacks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: deep learning
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Covert channel analysis directly identifies timing channels that could leak information.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices (reviews, testing) directly reduce introduction of timing-channel vulnerabilities in code.
Runtime monitoring of hardware/software behavior can detect anomalous timing patterns that indicate covert channels.
Vulnerability identification processes can surface timing-channel weaknesses during design or code analysis.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Detailed logging can reveal timing anomalies but does not prevent covert timing channels.
Continuous monitoring may detect timing-based exfiltration but does not eliminate the channel itself.
Network segmentation reduces attack surface but does not address intra-process timing channels.
Network segregation limits external timing observation but not internal covert timing.
Secure architecture principles can include timing-channel countermeasures but are not specific.
Secure coding guidelines may recommend constant-time algorithms but coverage is not guaranteed.