ghsa-r9fv-h47r-823f
Vulnerability from github
Published
2025-01-20 15:31
Modified
2025-01-27 21:30
Severity ?
4.1 (Medium) - CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Details

Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.

Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.

There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2024-13176",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-385",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2025-01-20T14:15:26Z",
      severity: "MODERATE",
   },
   details: "Issue summary: A timing side-channel which could potentially allow recovering\nthe private key exists in the ECDSA signature computation.\n\nImpact summary: A timing side-channel in ECDSA signature computations\ncould allow recovering the private key by an attacker. However, measuring\nthe timing would require either local access to the signing application or\na very fast network connection with low latency.\n\nThere is a timing signal of around 300 nanoseconds when the top word of\nthe inverted ECDSA nonce value is zero. This can happen with significant\nprobability only for some of the supported elliptic curves. In particular\nthe NIST P-521 curve is affected. To be able to measure this leak, the attacker\nprocess must either be located in the same physical computer or must\nhave a very fast network connection with low latency. For that reason\nthe severity of this vulnerability is Low.",
   id: "GHSA-r9fv-h47r-823f",
   modified: "2025-01-27T21:30:53Z",
   published: "2025-01-20T15:31:22Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-13176",
      },
      {
         type: "WEB",
         url: "https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844",
      },
      {
         type: "WEB",
         url: "https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467",
      },
      {
         type: "WEB",
         url: "https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902",
      },
      {
         type: "WEB",
         url: "https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65",
      },
      {
         type: "WEB",
         url: "https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f",
      },
      {
         type: "WEB",
         url: "https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded",
      },
      {
         type: "WEB",
         url: "https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86",
      },
      {
         type: "WEB",
         url: "https://openssl-library.org/news/secadv/20250120.txt",
      },
      {
         type: "WEB",
         url: "https://security.netapp.com/advisory/ntap-20250124-0005",
      },
      {
         type: "WEB",
         url: "http://www.openwall.com/lists/oss-security/2025/01/20/2",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
         type: "CVSS_V3",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.