CVE-2020-12607: Improper Verification of Cryptographic Signature in fastecdsa
(updated )
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.
References
- github.com/AntonKueltz/fastecdsa
- github.com/AntonKueltz/fastecdsa/commit/4a16daeaf139be20654ef58a9fe4c79dc030458c
- github.com/AntonKueltz/fastecdsa/commit/7b64e3efaa806b4daaf73bb5172af3581812f8de
- github.com/AntonKueltz/fastecdsa/commit/e592f106edd5acf6dacedfab2ad16fe6c735c9d1
- github.com/AntonKueltz/fastecdsa/issues/52
- github.com/advisories/GHSA-56wv-2wr9-3h9r
- github.com/pypa/advisory-database/tree/main/vulns/fastecdsa/PYSEC-2020-42.yaml
- nvd.nist.gov/vuln/detail/CVE-2020-12607
Code Behaviors & Features
Detect and mitigate CVE-2020-12607 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →