Filtered by vendor Starkbank
Subscribe
Total
5 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2021-43572 | 1 Starkbank | 1 Ecdsa-python | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages. | |||||
CVE-2021-43571 | 1 Starkbank | 1 Ecdsa-node | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
The verify function in the Stark Bank Node.js ECDSA library (ecdsa-node) 1.1.2 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages. | |||||
CVE-2021-43570 | 1 Starkbank | 1 Ecdsa-java | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
The verify function in the Stark Bank Java ECDSA library (ecdsa-java) 1.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages. | |||||
CVE-2021-43569 | 1 Starkbank | 1 Ecdsa-dotnet | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
The verify function in the Stark Bank .NET ECDSA library (ecdsa-dotnet) 1.3.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages. | |||||
CVE-2021-43568 | 1 Starkbank | 1 Elixir Ecdsa | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
The verify function in the Stark Bank Elixir ECDSA library (ecdsa-elixir) 1.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages. |