What is GHSA-HC3C-63HC-2R9F?

GHSA-HC3C-63HC-2R9F is a high-severity security vulnerability in libcrux-chacha20poly1305 (rust), affecting versions < 0.0.8. It is fixed in 0.0.8.

Which versions of libcrux-chacha20poly1305 are affected by GHSA-HC3C-63HC-2R9F?

libcrux-chacha20poly1305 (rust) versions < 0.0.8 is affected.

Is there a fix for GHSA-HC3C-63HC-2R9F?

Yes. GHSA-HC3C-63HC-2R9F is fixed in 0.0.8. Upgrade to this version or later.

Is GHSA-HC3C-63HC-2R9F exploitable, and should I be worried?

Whether GHSA-HC3C-63HC-2R9F 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-HC3C-63HC-2R9F 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-HC3C-63HC-2R9F in libcrux-chacha20poly1305

Q: Which versions of libcrux-chacha20poly1305 are affected by GHSA-HC3C-63HC-2R9F?

libcrux-chacha20poly1305 (rust) versions < 0.0.8 is affected.

Q: Is there a fix for GHSA-HC3C-63HC-2R9F?

Yes. GHSA-HC3C-63HC-2R9F is fixed in 0.0.8. Upgrade to this version or later.

Q: Is GHSA-HC3C-63HC-2R9F exploitable, and should I be worried?

Whether GHSA-HC3C-63HC-2R9F 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-HC3C-63HC-2R9F 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-HC3C-63HC-2R9F?

Upgrade libcrux-chacha20poly1305 to 0.0.8 or later.

Summary

libcrux: Potential Panic on Overlong Ciphertext Buffer

An application that passes in a ciphertext buffer of length greater
than ptxt.len() + TAG_LEN to libcrux_chacha20poly1305::encrypt or
libcrux_chacha20poly1305::xchacha20_poly1305::encrypt would
experience a panic.

Mitigation

The fix makes it so that libcrux_chacha20poly1305::encrypt and
libcrux_chacha20poly1305::xchacha20_poly1305::encrypt no longer
panic in this case, but instead write out the ciphertext and tag into
the first ptxt.len() + TAG_LEN bytes of the provided buffer.

Impact

An application where the length of the ciphertext buffer is under
attacker control could be made to crash.

Affected versions

libcrux-chacha20poly1305 (< 0.0.8)

Security releases

libcrux-chacha20poly1305 → 0.0.8 (rust)

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

Upgrade libcrux-chacha20poly1305 to 0.0.8 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is GHSA-HC3C-63HC-2R9F? GHSA-HC3C-63HC-2R9F is a high-severity security vulnerability in libcrux-chacha20poly1305 (rust), affecting versions < 0.0.8. It is fixed in 0.0.8.
Which versions of libcrux-chacha20poly1305 are affected by GHSA-HC3C-63HC-2R9F? libcrux-chacha20poly1305 (rust) versions < 0.0.8 is affected.
Is there a fix for GHSA-HC3C-63HC-2R9F? Yes. GHSA-HC3C-63HC-2R9F is fixed in 0.0.8. Upgrade to this version or later.
Is GHSA-HC3C-63HC-2R9F exploitable, and should I be worried? Whether GHSA-HC3C-63HC-2R9F 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-HC3C-63HC-2R9F 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-HC3C-63HC-2R9F? Upgrade libcrux-chacha20poly1305 to 0.0.8 or later.