GHSA-X5J2-G63M-F8G4
Vulnerability from github – Published: 2024-02-09 16:19 – Updated: 2024-04-15 19:41
VLAI?
Summary
pqc_kyber KyberSlash: division timings depending on secrets
Details
Various Kyber software libraries in various environments leak secret information into timing, specifically because
- these libraries include a line of code that divides a secret numerator by a public denominator,
- the number of CPU cycles for division in various environments varies depending on the inputs to the division, and
- this variation appears within the range of numerators used in these libraries.
The KyberSlash pages track which Kyber libraries have this issue, and include a FAQ about the issue.
Author
The KyberSlash pages were written by Daniel J. Bernstein. The FAQ originally said "I", but some people seemed to have trouble finding this authorship statement, so the FAQ now says "Bernstein" instead.
URL
The permanent link for the KyberSlash pages is https://kyberslash.cr.yp.to.
Mitigation status in pqc_kyber crate
The issues has not been resolved in the pqc_kyber crate. A third-party fork that mitigates this attack vector has been published as safe_pqc_kyber.
Severity ?
7.4 (High)
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "pqc_kyber"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.7.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [],
"github_reviewed": true,
"github_reviewed_at": "2024-02-09T16:19:53Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Various Kyber software libraries in various environments leak secret information into timing, specifically because\n\n * these libraries include a line of code that divides a secret numerator by a public denominator,\n * the number of CPU cycles for division in various environments varies depending on the inputs to the division, and\n * this variation appears within the range of numerators used in these libraries.\n\nThe KyberSlash pages track which Kyber [libraries](https://kyberslash.cr.yp.to/libraries.html) have this issue, and include a [FAQ](https://kyberslash.cr.yp.to/faq.html) about the issue.\n\n## Author\n\nThe KyberSlash pages were written by Daniel J. Bernstein. The FAQ originally said \"I\", but some people seemed to have trouble finding this authorship statement, so the FAQ now says \"Bernstein\" instead.\n\n## URL\n\nThe permanent link for the KyberSlash pages is [https://kyberslash.cr.yp.to](https://kyberslash.cr.yp.to).\n\n## Mitigation status in pqc_kyber crate\n\nThe issues has not been resolved in the `pqc_kyber` crate. A third-party fork that mitigates this attack vector has been published as [`safe_pqc_kyber`](https://crates.io/crates/safe_pqc_kyber).\n",
"id": "GHSA-x5j2-g63m-f8g4",
"modified": "2024-04-15T19:41:48Z",
"published": "2024-02-09T16:19:53Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Argyle-Software/kyber/issues/108"
},
{
"type": "WEB",
"url": "https://github.com/bwesterb/argyle-kyber/commit/b5c6ad13f4eece80e59c6ebeafd787ba1519f5f6"
},
{
"type": "PACKAGE",
"url": "https://github.com/Argyle-Software/kyber"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2023-0079.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "pqc_kyber KyberSlash: division timings depending on secrets"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…