GHSA-9WX7-JRVC-28MM

GHSA-9WX7-JRVC-28MM is a high-severity security vulnerability in starkbank-ecdsa (pip), affecting versions < 2.0.1. It is fixed in 2.0.1, 1.0.1, 1.3.2, 1.1.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Signature verification vulnerability in Stark Bank ecdsa libraries

An attacker can forge signatures on arbitrary messages that will verify for any public key. This may allow attackers to authenticate as any user within the Stark Bank platform, and bypass signature verification needed to perform operations on the platform, such as send payments and transfer funds. Additionally, the ability for attackers to forge signatures may impact other users and projects using these libraries in different and unforeseen ways.

Impact

Affected versions

starkbank-ecdsa (< 2.0.1) com.starkbank:ecdsa-java (= 1.0.0) starkbank-ecdsa (= 1.3.1) starkbank-ecdsa (= 1.1.2)

Security releases

starkbank-ecdsa → 2.0.1 (pip) com.starkbank:ecdsa-java → 1.0.1 (maven) starkbank-ecdsa → 1.3.2 (nuget) starkbank-ecdsa → 1.1.3 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

starkbank-ecdsa to 2.0.1 or later; com.starkbank:ecdsa-java to 1.0.1 or later; starkbank-ecdsa to 1.3.2 or later; starkbank-ecdsa to 1.1.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-9WX7-JRVC-28MM? GHSA-9WX7-JRVC-28MM is a high-severity security vulnerability in starkbank-ecdsa (pip), affecting versions < 2.0.1. It is fixed in 2.0.1, 1.0.1, 1.3.2, 1.1.3.
  2. Which packages are affected by GHSA-9WX7-JRVC-28MM?
    • starkbank-ecdsa (pip) (versions < 2.0.1)
    • com.starkbank:ecdsa-java (maven) (versions = 1.0.0)
  3. Is there a fix for GHSA-9WX7-JRVC-28MM? Yes. GHSA-9WX7-JRVC-28MM is fixed in 2.0.1, 1.0.1, 1.3.2, 1.1.3. Upgrade to this version or later.
  4. Is GHSA-9WX7-JRVC-28MM exploitable, and should I be worried? Whether GHSA-9WX7-JRVC-28MM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-9WX7-JRVC-28MM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-9WX7-JRVC-28MM?
    • Upgrade starkbank-ecdsa to 2.0.1 or later
    • Upgrade com.starkbank:ecdsa-java to 1.0.1 or later
    • Upgrade starkbank-ecdsa to 1.3.2 or later
    • Upgrade starkbank-ecdsa to 1.1.3 or later

Other vulnerabilities in starkbank-ecdsa

Stop the waste.
Protect your environment with Kodem.