GHSA-f8qm-hmm3-fv7f Namada-apps allows Excessive Computation in Mempool Validation
A malicious transaction can cause excessive computation in mempool validation, slowing down nodes and causing denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-f8qm-hmm3-fv7f?
GHSA-f8qm-hmm3-fv7f is a denial of service vulnerability in namada-apps, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Impact
A malicious transaction may cause an expensive computation in mempool validation.
A transaction with multiple repeated sections causes the section hash calculation used for signature validation to grow exponentially (and potentially even cubic) in proportion to number of sections. This may be used to significantly slow down operation of nodes.
Patches
This issue has been patched in apps version 1.1.0. The transaction sections are now being checked for uniqueness and the number of permitted sections contained in a single transaction has been limited to 10,000.
Workarounds
There are no workarounds and users are advised to upgrade.
Which versions are affected by GHSA-f8qm-hmm3-fv7f?
2 open source packages ship an affected version, including namada-apps.
| Package | Affected | Fixed in |
|---|---|---|
namada-apps crates.io | From 1.0.0 | 1.1.0 |
namada-apps crates.io | From 1.0.0 | 1.1.0 |
How do I fix GHSA-f8qm-hmm3-fv7f?
Upgrade namada-apps to 1.1.0 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is GHSA-f8qm-hmm3-fv7f being exploited?
There is no known exploitation of GHSA-f8qm-hmm3-fv7f in the wild and no public exploit code.