node-elliptic - Debian Package Tracker

general

source: node-elliptic (main)
version: 6.6.1+dfsg-1
maintainer: Debian Javascript Maintainers (archive) (DMD)
uploaders: Pirate Praveen [DMD] – Jonas Smedegaard [DMD]
arch: all
std-ver: 4.7.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 6.5.4~dfsg-1
oldstable: 6.5.4~dfsg-2
stable: 6.6.1+dfsg-1
testing: 6.6.1+dfsg-1
unstable: 6.6.1+dfsg-1

versioned links

6.5.4~dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
6.5.4~dfsg-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
6.6.1+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

node-elliptic

action needed

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2025-14505: The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

Created: 2026-01-09 Last update: 2026-01-10 17:00

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2025-14505: The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

Created: 2026-01-09 Last update: 2026-01-10 17:00

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2025-14505: The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

Created: 2026-01-09 Last update: 2026-01-10 17:00

6 security issues in bullseye high

There are 6 open security issues in bullseye.

1 important issue:

CVE-2025-14505: The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

5 issues postponed or untriaged:

CVE-2024-42459: (needs triaging) In the Elliptic package 6.5.6 for Node.js, EDDSA signature malleability occurs because there is a missing signature length check, and thus zero-valued bytes can be removed or appended.
CVE-2024-42460: (needs triaging) In the Elliptic package 6.5.6 for Node.js, ECDSA signature malleability occurs because there is a missing check for whether the leading bit of r and s is zero.
CVE-2024-42461: (needs triaging) In the Elliptic package 6.5.6 for Node.js, ECDSA signature malleability occurs because BER-encoded signatures are allowed.
CVE-2024-48948: (postponed; to be fixed through a stable update) The Elliptic package 6.5.7 for Node.js, in its for ECDSA implementation, does not correctly verify valid signatures if the hash contains at least four leading 0 bytes and when the order of the elliptic curve's base point is smaller than the hash, because of an _truncateToN anomaly. This leads to valid signatures being rejected. Legitimate transactions or communications may be incorrectly flagged as invalid.
CVE-2024-48949: (postponed; to be fixed through a stable update) The verify function in lib/elliptic/eddsa/index.js in the Elliptic package before 6.5.6 for Node.js omits "sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg()" validation.

Created: 2026-01-09 Last update: 2026-01-10 17:00

6 security issues in bookworm high

There are 6 open security issues in bookworm.

1 important issue:

CVE-2025-14505: The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.ietf.org/doc/html/rfc6979 ) has leading zeros and is susceptible to cryptanalysis, which can lead to secret key exposure. This happens, because the byte-length of 'k' is incorrectly computed, resulting in its getting truncated during the computation. Legitimate transactions or communications will be broken as a result. Furthermore, due to the nature of the fault, attackers could–under certain conditions–derive the secret key, if they could get their hands on both a faulty signature generated by a vulnerable version of Elliptic and a correct signature for the same inputs. This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).

5 issues left for the package maintainer to handle:

CVE-2024-42459: (needs triaging) In the Elliptic package 6.5.6 for Node.js, EDDSA signature malleability occurs because there is a missing signature length check, and thus zero-valued bytes can be removed or appended.
CVE-2024-42460: (needs triaging) In the Elliptic package 6.5.6 for Node.js, ECDSA signature malleability occurs because there is a missing check for whether the leading bit of r and s is zero.
CVE-2024-42461: (needs triaging) In the Elliptic package 6.5.6 for Node.js, ECDSA signature malleability occurs because BER-encoded signatures are allowed.
CVE-2024-48948: (needs triaging) The Elliptic package 6.5.7 for Node.js, in its for ECDSA implementation, does not correctly verify valid signatures if the hash contains at least four leading 0 bytes and when the order of the elliptic curve's base point is smaller than the hash, because of an _truncateToN anomaly. This leads to valid signatures being rejected. Legitimate transactions or communications may be incorrectly flagged as invalid.
CVE-2024-48949: (needs triaging) The verify function in lib/elliptic/eddsa/index.js in the Elliptic package before 6.5.6 for Node.js omits "sig.S().gte(sig.eddsa.curve.n) || sig.S().isNeg()" validation.

You can find information about how to handle these issues in the security team's documentation.

Created: 2024-08-02 Last update: 2026-01-10 17:00

3 new commits since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 6571c679cccdde1045eed57a591c83e19d46424c
Author: Xavier Guimard <yadd@debian.org>
Date:   Sun Mar 8 13:29:22 2026 +0100

    debian/watch version 5

commit e5295cc30f918b24fc29fda2ab53e6c17a046a6c
Author: Xavier Guimard <yadd@debian.org>
Date:   Sun Mar 8 13:28:12 2026 +0100

    Drop "Rules-Requires-Root: no"

commit 5aa8968f25ebcebf2130479f672901270c682be2
Author: Xavier Guimard <yadd@debian.org>
Date:   Sun Mar 8 13:28:12 2026 +0100

    Declare compliance with policy 4.7.3

Created: 2026-03-08 Last update: 2026-03-08 14:02

debian/patches: 1 patch to forward upstream low

Among the 2 debian patches available in version 6.6.1+dfsg-1 of the package, we noticed the following issues:

1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-02-06 18:21

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 4.7.0).

Created: 2025-02-21 Last update: 2025-12-23 20:00

news

[rss feed]

[2025-02-08] node-elliptic 6.6.1+dfsg-1 MIGRATED to testing (Debian testing watch)
[2025-02-06] Accepted node-elliptic 6.6.1+dfsg-1 (source) into unstable (Jérémy Lal)
[2024-10-11] node-elliptic 6.5.7+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-10-07] Accepted node-elliptic 6.5.7+dfsg-1 (source) into unstable (ghostman-pac) (signed by: Praveen Arimbrathodiyil)
[2022-11-23] node-elliptic 6.5.4~dfsg-2 MIGRATED to testing (Debian testing watch)
[2022-11-21] Accepted node-elliptic 6.5.4~dfsg-2 (source) into unstable (Jelmer Vernooĳ) (signed by: Jelmer Vernooij)
[2021-03-09] node-elliptic 6.5.4~dfsg-1 MIGRATED to testing (Debian testing watch)
[2021-03-03] Accepted node-elliptic 6.5.4~dfsg-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2020-09-20] Accepted node-elliptic 6.4.1~dfsg-1+deb10u1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Xavier Guimard)
[2020-06-22] node-elliptic 6.5.3~dfsg-1 MIGRATED to testing (Debian testing watch)
[2020-06-19] Accepted node-elliptic 6.5.3~dfsg-1 (source) into unstable (Jonas Smedegaard)
[2019-10-05] node-elliptic 6.5.1~dfsg-2 MIGRATED to testing (Debian testing watch)
[2019-10-02] Accepted node-elliptic 6.5.1~dfsg-2 (source) into unstable (Jonas Smedegaard)
[2019-09-23] node-elliptic 6.5.1~dfsg-1 MIGRATED to testing (Debian testing watch)
[2019-09-20] Accepted node-elliptic 6.5.1~dfsg-1 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2019-07-17] node-elliptic 6.5.0~dfsg-1 MIGRATED to testing (Debian testing watch)
[2019-07-15] Accepted node-elliptic 6.5.0~dfsg-1 (source) into unstable (Jonas Smedegaard)
[2019-01-13] node-elliptic 6.4.1~dfsg-1 MIGRATED to testing (Debian testing watch)
[2019-01-10] Accepted node-elliptic 6.4.1~dfsg-1 (source) into unstable (Jonas Smedegaard)
[2017-06-20] node-elliptic 6.4.0+dfsg-1 MIGRATED to testing (Debian testing watch)
[2017-05-03] Accepted node-elliptic 6.4.0+dfsg-1 (source all) into unstable, unstable (Pirate Praveen) (signed by: Praveen Arimbrathodiyil)

bugs [bug history graph]

all: 1
RC: 0
I&N: 1
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 6.6.1+dfsg-1