PatchTheCVEstarkbank vulnerabilities
Recent CVEs affecting starkbank products. 5 tracked.
starkbank has 5 tracked vulnerabilities, 5 critical. A fixed release or vendor patch exists for 1. Most recent: 2021-11-09. Highest priority: CVE-2021-43572 (score 62/100).
- CVE-2021-43572 CRITICAL 9.8 UPGRADE The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1
- CVE-2021-43571 CRITICAL 9.8 DOWNGRADE The verify function in the Stark Bank Node.js ECDSA library (ecdsa-node) 1.1.2 fails to check that the signatu
- CVE-2021-43570 CRITICAL 9.8 DOWNGRADE The verify function in the Stark Bank Java ECDSA library (ecdsa-java) 1.0.0 fails to check that the signature
- CVE-2021-43569 CRITICAL 9.8 DOWNGRADE The verify function in the Stark Bank .NET ECDSA library (ecdsa-dotnet) 1.3.1 fails to check that the signatur
- CVE-2021-43568 CRITICAL 9.8 DOWNGRADE The verify function in the Stark Bank Elixir ECDSA library (ecdsa-elixir) 1.0.0 fails to check that the signat
FAQ
How do I fix starkbank vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is starkbank being exploited right now?
None of the tracked starkbank CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which starkbank CVE should I patch first?
CVE-2021-43572 currently ranks highest (62/100): The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1.