GHSA-56wv-2wr9-3h9r
Suggest an improvement- Source
- https://github.com/advisories/GHSA-56wv-2wr9-3h9r
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/10/GHSA-56wv-2wr9-3h9r/GHSA-56wv-2wr9-3h9r.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/GHSA-56wv-2wr9-3h9r
- Aliases
- Published
- 2021-10-12T16:30:37Z
- Modified
- 2025-02-12T18:47:08.220015Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CVSS Calculator
- 8.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Improper Verification of Cryptographic Signature in fastecdsa
- Details
-
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<sup>-1</sup>, 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.
- Database specific
{ "nvd_published_at": "2020-06-02T21:15:00Z", "cwe_ids": [ "CWE-347" ], "severity": "HIGH", "github_reviewed_at": "2021-10-08T22:28:23Z", "github_reviewed": true }- References
-
- https://nvd.nist.gov/vuln/detail/CVE-2020-12607
- https://github.com/AntonKueltz/fastecdsa/issues/52
- https://github.com/AntonKueltz/fastecdsa/commit/4a16daeaf139be20654ef58a9fe4c79dc030458c
- https://github.com/AntonKueltz/fastecdsa/commit/7b64e3efaa806b4daaf73bb5172af3581812f8de
- https://github.com/AntonKueltz/fastecdsa/commit/e592f106edd5acf6dacedfab2ad16fe6c735c9d1
- https://github.com/AntonKueltz/fastecdsa
- https://github.com/advisories/GHSA-56wv-2wr9-3h9r
- https://github.com/pypa/advisory-database/tree/main/vulns/fastecdsa/PYSEC-2020-42.yaml
Affected packages
PyPI / fastecdsa
Package
- Name
- fastecdsa
- View open source insights on deps.dev
- Purl
- pkg:pypi/fastecdsa