What is GHSA-F6JH-HVG2-9525?

GHSA-F6JH-HVG2-9525 is a high-severity security vulnerability in github.com/kudelskisecurity/crystals-go (go), affecting versions < 0.0.0-20240116172146-2a6ca2d4e64d. It is fixed in 0.0.0-20240116172146-2a6ca2d4e64d.

Which versions of github.com/kudelskisecurity/crystals-go are affected by GHSA-F6JH-HVG2-9525?

github.com/kudelskisecurity/crystals-go (go) versions < 0.0.0-20240116172146-2a6ca2d4e64d is affected.

Is there a fix for GHSA-F6JH-HVG2-9525?

Yes. GHSA-F6JH-HVG2-9525 is fixed in 0.0.0-20240116172146-2a6ca2d4e64d. Upgrade to this version or later.

Is GHSA-F6JH-HVG2-9525 exploitable, and should I be worried?

Whether GHSA-F6JH-HVG2-9525 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-F6JH-HVG2-9525 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-F6JH-HVG2-9525?

Upgrade github.com/kudelskisecurity/crystals-go to 0.0.0-20240116172146-2a6ca2d4e64d or later.

GHSA-F6JH-HVG2-9525

Q: Which versions of github.com/kudelskisecurity/crystals-go are affected by GHSA-F6JH-HVG2-9525?

github.com/kudelskisecurity/crystals-go (go) versions < 0.0.0-20240116172146-2a6ca2d4e64d is affected.

Q: Is there a fix for GHSA-F6JH-HVG2-9525?

Yes. GHSA-F6JH-HVG2-9525 is fixed in 0.0.0-20240116172146-2a6ca2d4e64d. Upgrade to this version or later.

Q: Is GHSA-F6JH-HVG2-9525 exploitable, and should I be worried?

Whether GHSA-F6JH-HVG2-9525 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-F6JH-HVG2-9525 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-F6JH-HVG2-9525?

Upgrade github.com/kudelskisecurity/crystals-go to 0.0.0-20240116172146-2a6ca2d4e64d or later.

Summary

crystals-go vulnerable to KyberSlash (timing side-channel attack for Kyber)

Note

This library was written as part of a MsC student project in the Cybersecurity Team at Kudelski Security. It is not actively maintained anymore. It is only intended for research and testing. We discourage its use in any production environment. Kudelski Security does not use this library as part of their commercial offers or product. This has now been clarified on the project's README.

References

https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/ldX0ThYJuBo
http://kyberslash.cr.yp.to/

Impact

On some platforms, when an attacker can time decapsulation of Kyber on forged cipher texts, they could possibly learn (parts of) the secret key.

Affected versions

github.com/kudelskisecurity/crystals-go (< 0.0.0-20240116172146-2a6ca2d4e64d)

Security releases

github.com/kudelskisecurity/crystals-go → 0.0.0-20240116172146-2a6ca2d4e64d (go)

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

Patched in https://github.com/kudelskisecurity/crystals-go/pull/21

Frequently Asked Questions

What is GHSA-F6JH-HVG2-9525? GHSA-F6JH-HVG2-9525 is a high-severity security vulnerability in github.com/kudelskisecurity/crystals-go (go), affecting versions < 0.0.0-20240116172146-2a6ca2d4e64d. It is fixed in 0.0.0-20240116172146-2a6ca2d4e64d.
Which versions of github.com/kudelskisecurity/crystals-go are affected by GHSA-F6JH-HVG2-9525? github.com/kudelskisecurity/crystals-go (go) versions < 0.0.0-20240116172146-2a6ca2d4e64d is affected.
Is there a fix for GHSA-F6JH-HVG2-9525? Yes. GHSA-F6JH-HVG2-9525 is fixed in 0.0.0-20240116172146-2a6ca2d4e64d. Upgrade to this version or later.
Is GHSA-F6JH-HVG2-9525 exploitable, and should I be worried? Whether GHSA-F6JH-HVG2-9525 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-F6JH-HVG2-9525 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-F6JH-HVG2-9525? Upgrade github.com/kudelskisecurity/crystals-go to 0.0.0-20240116172146-2a6ca2d4e64d or later.