How severe is GHSA-f6jh-hvg2-9525?

No CVSS score has been assigned to GHSA-f6jh-hvg2-9525 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f6jh-hvg2-9525?

GHSA-f6jh-hvg2-9525 affects the following packages: github.com/kudelskisecurity/crystals-go (Go). Ecosystems affected: Go.

How do I fix GHSA-f6jh-hvg2-9525?

Update github.com/kudelskisecurity/crystals-go to 0.0.0-20240116172146-2a6ca2d4e64d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6jh-hvg2-9525 is resolved across your whole dependency graph.

How do I detect GHSA-f6jh-hvg2-9525 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kudelskisecurity/crystals-go. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f6jh-hvg2-9525 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f6jh-hvg2-9525?

O3 pinpoints whether GHSA-f6jh-hvg2-9525 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f6jh-hvg2-9525 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f6jh-hvg2-9525 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-f6jh-hvg2-9525 published, and has it been updated?

GHSA-f6jh-hvg2-9525 was published on January 17, 2024 and was last updated on May 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-f6jh-hvg2-9525

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

Also known asGO-2024-2469

Published

Jan 17, 2024

Updated

May 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/kudelskisecurity/crystals-go

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

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

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/

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kudelskisecurity/crystals-go`	all versions	0.0.0-20240116172146-2a6ca2d4e64d

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kudelskisecurity/crystals-go. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/kudelskisecurity/crystals-go to 0.0.0-20240116172146-2a6ca2d4e64d or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f6jh-hvg2-9525 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-f6jh-hvg2-9525 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f6jh-hvg2-9525. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Patches Patched in https://github.com/kudelskisecurity/crystals-go/pull/21 ### 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 c

O3 Security · Impact-Aware SCA

Is GHSA-f6jh-hvg2-9525 in your dependencies?

O3 detects GHSA-f6jh-hvg2-9525 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works