GHSA-F6JH-HVG2-9525

Vulnerability from github – Published: 2024-01-17 22:06 – Updated: 2024-05-20 22:05
VLAI?
Summary
crystals-go vulnerable to KyberSlash (timing side-channel attack for Kyber)
Details

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/

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/kudelskisecurity/crystals-go"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.0-20240116172146-2a6ca2d4e64d"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": true,
    "github_reviewed_at": "2024-01-17T22:06:20Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\nOn some platforms, when an attacker can time decapsulation of Kyber on forged cipher texts, they could possibly learn (parts of) the secret key.\n\n### Patches\nPatched in https://github.com/kudelskisecurity/crystals-go/pull/21\n\n### Note\nThis 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\u0027s README.\n\n### References\nhttps://groups.google.com/a/list.nist.gov/g/pqc-forum/c/ldX0ThYJuBo\nhttp://kyberslash.cr.yp.to/",
  "id": "GHSA-f6jh-hvg2-9525",
  "modified": "2024-05-20T22:05:23Z",
  "published": "2024-01-17T22:06:20Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/kudelskisecurity/crystals-go/security/advisories/GHSA-f6jh-hvg2-9525"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kudelskisecurity/crystals-go/issues/19"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kudelskisecurity/crystals-go/pull/20"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kudelskisecurity/crystals-go/pull/21"
    },
    {
      "type": "WEB",
      "url": "https://github.com/kudelskisecurity/crystals-go/commit/2a6ca2d4e64d18dd6e8fbb4e48e22c2510118505"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/kudelskisecurity/crystals-go"
    },
    {
      "type": "WEB",
      "url": "https://kyberslash.cr.yp.to/faq"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "crystals-go vulnerable to KyberSlash (timing side-channel attack for Kyber)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…