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

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Feb 2025

## 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 | Ecosystem | 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.

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

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f8qm-hmm3-fv7f and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of GHSA-f8qm-hmm3-fv7f in the wild and no public exploit code.

Affected packages and fixed versions:
- namada-apps (crates.io): affected from 1.0.0; fixed in 1.1.0
- namada-apps (crates.io): affected from 1.0.0; fixed in 1.1.0

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/GHSA-f8qm-hmm3-fv7f/ (Markdown: https://insights.sbomify.com/GHSA-f8qm-hmm3-fv7f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f8qm-hmm3-fv7f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f8qm-hmm3-fv7f/
Summaries are generated and may contain mistakes; the official description above is the record.