What is GHSA-8327-84CJ-8XJM?

GHSA-8327-84CJ-8XJM is a medium-severity uncontrolled resource consumption vulnerability in alloy-json-abi (rust), affecting versions <= 0.7.7. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-8327-84CJ-8XJM?

GHSA-8327-84CJ-8XJM has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of alloy-json-abi are affected by GHSA-8327-84CJ-8XJM?

alloy-json-abi (rust) versions <= 0.7.7 is affected.

Is there a fix for GHSA-8327-84CJ-8XJM?

No fixed version is listed for GHSA-8327-84CJ-8XJM yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-8327-84CJ-8XJM exploitable, and should I be worried?

Whether GHSA-8327-84CJ-8XJM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-8327-84CJ-8XJM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-8327-84CJ-8XJM in alloy-json-abi

Q: How severe is GHSA-8327-84CJ-8XJM?

GHSA-8327-84CJ-8XJM has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of alloy-json-abi are affected by GHSA-8327-84CJ-8XJM?

alloy-json-abi (rust) versions <= 0.7.7 is affected.

Q: Is there a fix for GHSA-8327-84CJ-8XJM?

No fixed version is listed for GHSA-8327-84CJ-8XJM yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-8327-84CJ-8XJM exploitable, and should I be worried?

Whether GHSA-8327-84CJ-8XJM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-8327-84CJ-8XJM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-8327-84CJ-8XJM?

No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

Summary

Stack overflow when parsing specially crafted JSON ABI strings

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.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-8327-84CJ-8XJM has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

alloy-json-abi (<= 0.7.7)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for GHSA-8327-84CJ-8XJM yet.

In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-8327-84CJ-8XJM? GHSA-8327-84CJ-8XJM is a medium-severity uncontrolled resource consumption vulnerability in alloy-json-abi (rust), affecting versions <= 0.7.7. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-8327-84CJ-8XJM? GHSA-8327-84CJ-8XJM has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of alloy-json-abi are affected by GHSA-8327-84CJ-8XJM? alloy-json-abi (rust) versions <= 0.7.7 is affected.
Is there a fix for GHSA-8327-84CJ-8XJM? No fixed version is listed for GHSA-8327-84CJ-8XJM yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-8327-84CJ-8XJM exploitable, and should I be worried? Whether GHSA-8327-84CJ-8XJM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-8327-84CJ-8XJM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-8327-84CJ-8XJM? No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.