CVE-2021-43572: Universal Signature Forgery in Stark Bank Python ECDSA Library
- Vendor
- Starkbank
A critical vulnerability exists in the Stark Bank Python ECDSA library (ecdsa-python) before version 2.0.1, where the verify function fails to check that the ECDSA signature components (r, s) are non-zero. This allows an attacker to forge signatures for arbitrary messages that will verify against any public key, due to the acceptance of (r, s) = (0, 0) as a valid signature. The flaw is due to missing range checks for the r and s values during signature verification.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Attackers can forge valid ECDSA signatures for any message and public key, effectively bypassing authentication and authorization mechanisms that rely on ECDSA signatures. This could allow unauthorized actions such as payments, fund transfers, or impersonation of any user on systems using the vulnerable library, with potentially severe financial and security consequences.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, implement additional signature validation to ensure r and s are non-zero and within the valid range for the curve in use. Monitor for suspicious or anomalous signature verification activity until the library can be updated.
Remediation
Patch, then assume compromise.
Upgrade the Stark Bank Python ECDSA library to version 2.0.1 or later, which includes proper validation of the r and s signature components. Ensure all dependent systems and applications are using the patched version.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2021-43572 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2021-43572 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2021-43572?
- Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2021-43572.
- Is there a patch for CVE-2021-43572?
- Upgrade the Stark Bank Python ECDSA library to version 2.0.1 or later, which includes proper validation of the r and s signature components. Ensure all dependent systems and applications are using the patched version.
- What products are affected by CVE-2021-43572?
- Starkbank Ecdsa-Python.
- How severe is CVE-2021-43572?
- CVE-2021-43572 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.2% (70th percentile) as of Oct 16, 2026.
Recent activity
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.