# GHSA-82vg-5v4f-f9wq: Namada-apps can Crash with Excessive Computation in Mempool Validation

> A malicious transaction with many signatures causes an integer overflow, crashing the Namada node during mempool validation.

- **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-82vg-5v4f-f9wq?

GHSA-82vg-5v4f-f9wq is a 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 a crash in mempool validation.

A transaction with authorization section containing 256 public keys or more with valid matching signatures triggers an integer overflow in signature verification that causes a the node to panic.

### Patches

This issue has been patched in apps version 1.1.0. The mempool validation has been fixed to avoid overflow.

### Workarounds

There are no workarounds and users are advised to upgrade.

## Which versions are affected by GHSA-82vg-5v4f-f9wq?

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-82vg-5v4f-f9wq?

Upgrade namada-apps to 1.1.0 or later.

## Is GHSA-82vg-5v4f-f9wq being exploited?

There is no known exploitation of GHSA-82vg-5v4f-f9wq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-82vg-5v4f-f9wq and fix it if it is affected.

What it is: GHSA-82vg-5v4f-f9wq is a 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-82vg-5v4f-f9wq 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-82vg-5v4f-f9wq/ (Markdown: https://insights.sbomify.com/GHSA-82vg-5v4f-f9wq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-82vg-5v4f-f9wq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-82vg-5v4f-f9wq/
Summaries are generated and may contain mistakes; the official description above is the record.