https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 16:10:51 +0000 https://cve.radiocsirt.org/vuln/cnvd-2021-37776 cnvd-2021-37776 https://cve.radiocsirt.org/vuln/cnvd-2021-37776 https://cve.radiocsirt.org/vuln/euvd-2026-41323 EUVD-2026-41323 https://cve.radiocsirt.org/vuln/euvd-2026-41323 https://cve.radiocsirt.org/vuln/fkie_cve-2020-12607 <p>An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.</p> <p>An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-12607 https://cve.radiocsirt.org/vuln/ghsa-56wv-2wr9-3h9r <p><strong>Affected:</strong> PyPI: fastecdsa</p> <p>An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s&lt;sup&gt;-1&lt;/sup&gt;, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.</p> <p><strong>Affected:</strong> PyPI: fastecdsa</p> <p>An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s&lt;sup&gt;-1&lt;/sup&gt;, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.</p> https://cve.radiocsirt.org/vuln/ghsa-56wv-2wr9-3h9r https://cve.radiocsirt.org/vuln/gsd-2020-12607 gsd-2020-12607 https://cve.radiocsirt.org/vuln/gsd-2020-12607 https://cve.radiocsirt.org/vuln/pysec-2020-42 <p><strong>Affected:</strong> PyPI: fastecdsa</p> <p>An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.</p> <p><strong>Affected:</strong> PyPI: fastecdsa</p> <p>An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a usability problem. There are some threat models where an attacker can benefit by successfully guessing users for whom signature verification will fail.</p> https://cve.radiocsirt.org/vuln/pysec-2020-42