Advisory record · GHSA-r28h-x6hv-2fq3

Improper Verification of Cryptographic Signature in starkbank-ecdsa

CVSS 9.8 CriticalCriticalEPSS 0.010 · 64th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 10 Nov 2021, 20:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.starkbank.ellipticcurve:starkbank-ecdsaMaven<1.0.11.0.1
Identifiers
GHSA-r28h-x6hv-2fq3 · CVE-2021-43570
Weakness (CWE)
CWE-347
Published
10 Nov 2021
Updated
20 Jan 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of starkbank-ecdsa below 1.0.1 are affected. The verify function does not check that the signature is non-zero, so an attacker can forge signatures on arbitrary messages without needing a valid key. Upgrade to starkbank-ecdsa 1.0.1 or later; no workaround is listed.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.010, the 64th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.