CVE-2025-66692
BaseFortify
Publication date: 2026-01-20
Last updated on: 2026-01-30
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| trustwallet | trust_wallet_core | to 4.4.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-126 | The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-66692 is a buffer over-read vulnerability in the PublicKey::verify() method of Binance - Trust Wallet Core before commit 5668c67. The method accepts a signature input without validating its length, which should be exactly 64 bytes for cryptographic verification. If a crafted signature with an invalid length is provided, the function reads beyond the buffer boundary, causing out-of-bounds memory access. This leads to potential application crashes (Denial of Service) and may expose adjacent memory contents. The vulnerability arises because the signature length was not checked before cryptographic functions were called, allowing attackers to exploit this by sending malformed signatures. [2]
How can this vulnerability impact me? :
This vulnerability can cause a Denial of Service (DoS) by crashing the application when it processes a crafted signature with an invalid length. The crash results from a buffer over-read in the PublicKey::verify() method. Additionally, there is a risk of information disclosure, where up to 55 bytes of adjacent memory could be exposed due to the out-of-bounds read. This can disrupt blockchain operations relying on Trust Wallet Core, affecting transaction verification and potentially causing service interruptions. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the Trust Wallet Core's PublicKey::verify() function with crafted inputs that have invalid signature lengths (less than 64 bytes). For example, running unit tests similar to the 'VerifyInvalidLength' test case that attempts to verify signatures with incorrect lengths (e.g., 63 bytes or 10 bytes) can reveal if the system is vulnerable by causing crashes or segmentation faults. There are no specific network commands provided, but testing the application with malformed signature inputs that trigger buffer over-read can help detect the issue. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating Trust Wallet Core to version 4.4.0 or later, which includes the patch that adds signature length validation in the PublicKey::verify() function. This patch rejects any signature that does not have a valid length (64 or 65 bytes depending on key type), preventing buffer over-read and denial of service. If updating is not immediately possible, ensure that any inputs to PublicKey::verify() are validated for correct signature length before processing. [1, 2]