CVE-2025-49600
BaseFortify
Publication date: 2025-07-04
Last updated on: 2025-07-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| arm | mbed_tls | From 3.3.0 (inc) to 3.6.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-325 | The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in MbedTLS versions 3.3.0 before 3.6.4 involves the mbedtls_lms_verify function potentially accepting invalid LMS signatures if hash computation fails and errors are not checked. Specifically, unchecked return values from internal Merkle tree functions can lead to uninitialized data being used, allowing an attacker who can induce faults in a hardware hash accelerator to bypass signature verification by reusing stale stack data, resulting in acceptance of forged signatures.
How can this vulnerability impact me? :
The vulnerability allows an attacker capable of inducing faults in hardware hash accelerators to bypass LMS signature verification, potentially enabling signature forgery. This could lead to acceptance of invalid signatures, undermining the integrity of cryptographic operations that rely on LMS signatures, and possibly allowing unauthorized actions or data to be accepted as valid.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update MbedTLS to version 3.6.4 or later where the issue with unchecked return values in mbedtls_lms_verify is fixed. Additionally, avoid using hardware-accelerated hashing modules that may be susceptible to fault injection attacks until patched. Implement hardware protections against fault injection if possible.