Skip to content
Fencer Intel
high —

GHSA-p4v8-jgcv-9g75 json

safe_pqc_kyber leaks parts of secret keys

published 2y ago modified 2y ago

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, and in particular when the attacker can forge cipher texts, they can learn (parts of) the secret key.

Does not apply to ephemeral usage, such as when used in the regular way in TLS.

### Patches Patched in 0.6.2.

### References - [kyberslash.cr.yp.to](https://kyberslash.cr.yp.to)

Patch / fix

  • crates.io safe_pqc_kyber 0.6.2

Is GHSA-p4v8-jgcv-9g75 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io safe_pqc_kyber
<0.6.2
0.6.2

References

Sources

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.