What is GHSA-2C6H-4899-WJXR?

GHSA-2C6H-4899-WJXR is a high-severity out-of-bounds read vulnerability in scaly (rust), affecting versions <= 0.0.37. No fixed version is listed yet. A read operation accesses a memory location beyond the intended buffer boundary.

Which versions of scaly are affected by GHSA-2C6H-4899-WJXR?

scaly (rust) versions <= 0.0.37 is affected.

Is there a fix for GHSA-2C6H-4899-WJXR?

No fixed version is listed for GHSA-2C6H-4899-WJXR yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-2C6H-4899-WJXR exploitable, and should I be worried?

Whether GHSA-2C6H-4899-WJXR 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-2C6H-4899-WJXR 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-2C6H-4899-WJXR in scaly

Q: Which versions of scaly are affected by GHSA-2C6H-4899-WJXR?

scaly (rust) versions <= 0.0.37 is affected.

Q: Is there a fix for GHSA-2C6H-4899-WJXR?

No fixed version is listed for GHSA-2C6H-4899-WJXR yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-2C6H-4899-WJXR exploitable, and should I be worried?

Whether GHSA-2C6H-4899-WJXR 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-2C6H-4899-WJXR 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-2C6H-4899-WJXR?

No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked APIs and run with address sanitizers.

Summary

scaly: Multiple soundness issues in Rust safe APIs

Affected versions contain multiple safe APIs that can trigger undefined behavior:

Array<T>::index can perform an out-of-bounds read.
String::get_length can perform an out-of-bounds read.
String::append_character can perform an invalid write.
String::to_c_string can perform an out-of-bounds write.

These issues were reproduced against scaly 0.0.37 under Miri. The crate is unmaintained.

Impact

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

Affected versions

scaly (<= 0.0.37)

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-2C6H-4899-WJXR yet.

In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked APIs and run with address sanitizers.

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

Frequently Asked Questions

What is GHSA-2C6H-4899-WJXR? GHSA-2C6H-4899-WJXR is a high-severity out-of-bounds read vulnerability in scaly (rust), affecting versions <= 0.0.37. No fixed version is listed yet. A read operation accesses a memory location beyond the intended buffer boundary.
Which versions of scaly are affected by GHSA-2C6H-4899-WJXR? scaly (rust) versions <= 0.0.37 is affected.
Is there a fix for GHSA-2C6H-4899-WJXR? No fixed version is listed for GHSA-2C6H-4899-WJXR yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-2C6H-4899-WJXR exploitable, and should I be worried? Whether GHSA-2C6H-4899-WJXR 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-2C6H-4899-WJXR 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-2C6H-4899-WJXR? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked APIs and run with address sanitizers.