https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 10:54:53 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0901 certfr-2026-avi-0901 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0901 https://cve.radiocsirt.org/vuln/euvd-2026-265237 EUVD-2026-265237 https://cve.radiocsirt.org/vuln/euvd-2026-265237 https://cve.radiocsirt.org/vuln/fkie_cve-2025-14505 <p>The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &#39;k&#39; (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 &#39;k&#39; 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.</p> <p>This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).</p> <p>The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &#39;k&#39; (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 &#39;k&#39; 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.</p> <p>This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-14505 https://cve.radiocsirt.org/vuln/ghsa-848j-6mx2-7j84 <p><strong>Affected:</strong> npm: elliptic</p> <p>The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &#39;k&#39; (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 &#39;k&#39; 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.</p> <p>This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).</p> <p><strong>Affected:</strong> npm: elliptic</p> <p>The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &#39;k&#39; (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 &#39;k&#39; 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.</p> <p>This issue affects all known versions of Elliptic (at the time of writing, versions less than or equal to 6.6.1).</p> https://cve.radiocsirt.org/vuln/ghsa-848j-6mx2-7j84 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-14505 <p><strong>Affected:</strong> Ubuntu:18.04:LTS: node-elliptic, Ubuntu:20.04:LTS: node-elliptic, Ubuntu:22.04:LTS: node-elliptic, Ubuntu:24.04:LTS: node-elliptic, Ubuntu:25.10: node-elliptic, Ubuntu:26.04:LTS: node-elliptic</p> <p>The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &#39;k&#39; (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 &#39;k&#39; 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).</p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: node-elliptic, Ubuntu:20.04:LTS: node-elliptic, Ubuntu:22.04:LTS: node-elliptic, Ubuntu:24.04:LTS: node-elliptic, Ubuntu:25.10: node-elliptic, Ubuntu:26.04:LTS: node-elliptic</p> <p>The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of &#39;k&#39; (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 &#39;k&#39; 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).</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-14505