ghsa-434g-2637-qmqr
Vulnerability from github
Published
2024-10-10 03:30
Modified
2025-03-25 20:10
Severity ?
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
2.7 (Low) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
2.7 (Low) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Summary
Elliptic's verify function omits uniqueness validation
Details
The Elliptic package 6.5.5 for Node.js for EDDSA implementation does not perform the required check if the signature proof(s) is within the bounds of the order n of the base point of the elliptic curve, leading to signature malleability. Namely, the verify
function in lib/elliptic/eddsa/index.js
omits sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg()
validation.
This vulnerability could have a security-relevant impact if an application relies on the uniqueness of a signature.
{ affected: [ { package: { ecosystem: "npm", name: "elliptic", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "6.5.6", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2024-48949", ], database_specific: { cwe_ids: [ "CWE-347", ], github_reviewed: true, github_reviewed_at: "2024-10-10T21:00:04Z", nvd_published_at: "2024-10-10T01:15:11Z", severity: "LOW", }, details: "The Elliptic package 6.5.5 for Node.js for EDDSA implementation does not perform the required check if the signature proof(s) is within the bounds of the order n of the base point of the elliptic curve, leading to signature malleability. Namely, the `verify` function in `lib/elliptic/eddsa/index.js` omits `sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg()` validation.\n\nThis vulnerability could have a security-relevant impact if an application relies on the uniqueness of a signature.", id: "GHSA-434g-2637-qmqr", modified: "2025-03-25T20:10:14Z", published: "2024-10-10T03:30:44Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-48949", }, { type: "WEB", url: "https://github.com/indutny/elliptic/commit/7ac5360118f74eb02da73bdf9f24fd0c72ff5281", }, { type: "PACKAGE", url: "https://github.com/indutny/elliptic", }, { type: "WEB", url: "https://github.com/indutny/elliptic/compare/v6.5.5...v6.5.6", }, { type: "WEB", url: "https://security.netapp.com/advisory/ntap-20241227-0003", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", type: "CVSS_V3", }, { score: "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U", type: "CVSS_V4", }, ], summary: "Elliptic's verify function omits uniqueness validation", }
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.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
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.