GHSA-f6jh-hvg2-9525 json
crystals-go vulnerable to KyberSlash (timing side-channel attack for Kyber)
published 2y ago modified 2y ago also GO-2024-2469
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### 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/
Patch / fix
- go github.com/kudelskisecurity/crystals-go 0.0.0-20240116172146-2a6ca2d4e64d
- github.com/kudelskisecurity/crystals-go@2a6ca2d commit
- github.com/kudelskisecurity/crystals-go#20 pull request
- github.com/kudelskisecurity/crystals-go#21 pull request
Is GHSA-f6jh-hvg2-9525 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/kudelskisecurity/crystals-go | <0.0.0-20240116172146-2a6ca2d4e64d |
0.0.0-20240116172146-2a6ca2d4e64d |
References
-
github.com
/kudelskisecurity/crystals-go/pull/20
web, patch
-
github.com
/kudelskisecurity/crystals-go/pull/21
web, patch
-
github.com
/kudelskisecurity/crystals-go/commit/2a6ca2d4e64d18dd6e8fbb4e48e22c2510118505
web
-
github.com
/kudelskisecurity/crystals-go/security/advisories/GHSA-f6jh-hvg2-9525
web, advisory
-
github.com
/kudelskisecurity/crystals-go/issues/19
web, report
-
github.com
/kudelskisecurity/crystals-go
package
-
kyberslash.cr.yp.to
/faq
web
Sources
- GitHub Advisory GHSA-f6jh-hvg2-9525
- OSV GO-2024-2469
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.