From 19130d644d2631df0d100aec2cbf26a9b092683e Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Fri, 23 Feb 2024 16:42:12 +0000 Subject: [PATCH] Publish GHSA-rc4p-p3j9-6577 --- .../2024/02/GHSA-rc4p-p3j9-6577/GHSA-rc4p-p3j9-6577.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advisories/github-reviewed/2024/02/GHSA-rc4p-p3j9-6577/GHSA-rc4p-p3j9-6577.json b/advisories/github-reviewed/2024/02/GHSA-rc4p-p3j9-6577/GHSA-rc4p-p3j9-6577.json index 1536306a72c..6bcd81f8516 100644 --- a/advisories/github-reviewed/2024/02/GHSA-rc4p-p3j9-6577/GHSA-rc4p-p3j9-6577.json +++ b/advisories/github-reviewed/2024/02/GHSA-rc4p-p3j9-6577/GHSA-rc4p-p3j9-6577.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-rc4p-p3j9-6577", - "modified": "2024-02-22T21:41:47Z", + "modified": "2024-02-23T16:40:49Z", "published": "2024-02-22T21:41:47Z", "aliases": [ ], "summary": "pypqc private key retrieval vulnerability", - "details": "### Impact\nAn attacker able to submit many ciphertexts against a single private key, and to get responses in real-time, could recover the private key. This vulnerability has been named KyberSlash.\n\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:F/RL:O/RC:C\n\n### Patches\nVersion 0.0.6.1 and newer of PyPQC is patched.\n\n### Workarounds\nNo workarounds have been reported. The 0.0.6 -> 0.0.6.1 upgrade should be a drop-in replacement; it has no known breaking changes.\n\n### References\n1. This was partially patched (\"KyberSlash 1\") in the reference implementation by Peter Schwabe on December 1st, 2023. \n https://www.github.com/pq-crystals/kyber/commit/dda29cc63af721981ee2c831cf00822e69be3220\n\n2. This was reported as a security vulnerability by Daniel J. Bernstein on December 15th, 2023. \n https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hWqFJCucuj4/m/-Z-jm_k9AAAJ\n\n3. A webpage was stood up for authoritative reference about this by Daniel J. Bernstein on December 19th, 2023. \n https://kyberslash.cr.yp.to/\n\n4. This was acknowledged as a security vulnerability by Thom Wiggers on December 19th, 2023. \n https://www.github.com/PQClean/PQClean/issues/533\n\n5. This was completely patched (\"KyberSlash 2\") in the reference implementation by Peter Schwabe on December 29th, 2023.\n https://www.github.com/pq-crystals/kyber/commit/11d00ff1f20cfca1f72d819e5a45165c1e0a2816\n\n6. A proof-of-concept exploit was published by Daniel J. Bernstein on December 30th, 2023. \n https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/ldX0ThYJuBo/m/uIOqRF5BAwAJ\n\n7. This was completely patched in upstream by Thom Wiggers on January 25th, 2024. \n https://www.github.com/PQClean/PQClean/pull/534#event-11595728485\n\n8. This was completely patched in pypqc \\(including upload to PyPI\\) on January 26th, 2024. \n https://www.github.com/JamesTheAwesomeDude/pypqc/commit/b33fec8cd36e865f8db6215c64b2d01f429a1ed6", + "details": "### Impact\nFor `kyber512`, `kyber768`, and `kyber1024` only: An attacker able to submit many ciphertexts against a single private key, and to get responses in real-time, could recover the private key. This attack has been named KyberSlash\n\nCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:F/RL:O/RC:C\n\n### Patches\nVersion 0.0.6.1 and newer of PyPQC is patched.\n\n### Workarounds\nNo workarounds have been reported. The 0.0.6 -> 0.0.6.1 upgrade should be a drop-in replacement; it has no known breaking changes.\n\n### References\n1. This was partially patched (\"KyberSlash 1\") in the reference implementation by Peter Schwabe on December 1st, 2023. \n https://www.github.com/pq-crystals/kyber/commit/dda29cc63af721981ee2c831cf00822e69be3220\n\n2. This was reported as a security vulnerability by Daniel J. Bernstein on December 15th, 2023. \n https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/hWqFJCucuj4/m/-Z-jm_k9AAAJ\n\n3. A webpage was stood up for authoritative reference about this by Daniel J. Bernstein on December 19th, 2023. \n https://kyberslash.cr.yp.to/\n\n4. This was acknowledged as a security vulnerability by Thom Wiggers on December 19th, 2023. \n https://www.github.com/PQClean/PQClean/issues/533\n\n5. This was completely patched (\"KyberSlash 2\") in the reference implementation by Peter Schwabe on December 29th, 2023.\n https://www.github.com/pq-crystals/kyber/commit/11d00ff1f20cfca1f72d819e5a45165c1e0a2816\n\n6. Further details were reported by Prasanna Ravi and Matthias Kannwischer on December 30th, 2023. \n https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/ldX0ThYJuBo/m/ovODsdY7AwAJ\n\n7. A proof-of-concept exploit was published by Daniel J. Bernstein on December 30th, 2023. \n https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/ldX0ThYJuBo/m/uIOqRF5BAwAJ\n\n8. This was completely patched in upstream by Thom Wiggers on January 25th, 2024. \n https://www.github.com/PQClean/PQClean/pull/534#event-11595728485\n\n9. This was completely patched in pypqc \\(including upload to PyPI\\) on January 26th, 2024. \n https://www.github.com/JamesTheAwesomeDude/pypqc/commit/b33fec8cd36e865f8db6215c64b2d01f429a1ed6", "severity": [ { "type": "CVSS_V3",