GHSA-8327-84cj-8xjm json
Stack overflow when parsing specially crafted JSON ABI strings
published 2y ago modified last yr. also RUSTSEC-2024-0362
- cvss
- 5.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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).
Patch / fix
Is GHSA-8327-84cj-8xjm in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | alloy-json-abi | <=0.7.7 >=0.0.0-0, <0.7.7 |
0.7.7 |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
Sources
- GitHub Advisory GHSA-8327-84cj-8xjm
- OSV RUSTSEC-2024-0362
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.