# GHSA-8327-84cj-8xjm: Stack overflow when parsing specially crafted JSON ABI strings

> Attackers can cause a denial of service by sending specially crafted JSON ABI strings that trigger a stack overflow in the alloy-json-abi crate.

- **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:** 30 Jul 2024
- **Also known as:** RUSTSEC-2024-0362

## What is GHSA-8327-84cj-8xjm?

GHSA-8327-84cj-8xjm is a denial of service vulnerability in alloy-json-abi, published on 30 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of the `alloy-json-abi` crate did not properly handle parsing of malformatted JSON ABI strings. The `JsonAbi::parse` method can be tricked into a stack overflow when processing specially crafted input. 

This stack overflow can lead to a crash of the application using this crate, potentially causing a denial of service.

The flaw was corrected in commit [4790c47](https://github.com/alloy-rs/core/commit/4790c47518024bd391bbd6815b00f501bad76a15).

## Which versions are affected by GHSA-8327-84cj-8xjm?

3 open source packages ship an affected version, including alloy-json-abi.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `alloy-json-abi` | crates.io | All versions to 0.7.7 | None |
| `alloy-json-abi` | crates.io | All versions to 0.7.7 | None |
| `alloy-json-abi` | crates.io | From 0.0.0-0 | 0.7.7 |

## How do I fix GHSA-8327-84cj-8xjm?

Upgrade alloy-json-abi to 0.7.7 or later.

## Is GHSA-8327-84cj-8xjm being exploited?

There is no known exploitation of GHSA-8327-84cj-8xjm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8327-84cj-8xjm and fix it if it is affected.

What it is: GHSA-8327-84cj-8xjm is a denial of service vulnerability in alloy-json-abi, published on 30 Jul 2024. 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-8327-84cj-8xjm in the wild and no public exploit code.

Affected packages and fixed versions:
- alloy-json-abi (crates.io): affected all versions up to 0.7.7; no fix listed
- alloy-json-abi (crates.io): affected all versions up to 0.7.7; no fix listed
- alloy-json-abi (crates.io): affected from 0.0.0-0; fixed in 0.7.7

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-8327-84cj-8xjm/ (Markdown: https://insights.sbomify.com/GHSA-8327-84cj-8xjm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8327-84cj-8xjm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8327-84cj-8xjm/
Summaries are generated and may contain mistakes; the official description above is the record.