Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven📦 npm.NET NuGet🐍 PyPI

GHSA-9wx7-jrvc-28mm

Signature verification vulnerability in Stark Bank ecdsa libraries

Published
Nov 8, 2021
Updated
Dec 6, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Blast Radius

4 pkgs affected
com.starkbank:ecdsa-java📦starkbank-ecdsa.NETstarkbank-ecdsa🐍starkbank-ecdsa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, npm, NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.starkbank:ecdsa-java1.0.0&&< 1.0.11.0.1
📦npmstarkbank-ecdsa1.1.2&&< 1.1.31.1.3
.NETNuGetstarkbank-ecdsa1.3.1&&< 1.3.21.3.2
🐍PyPIstarkbank-ecdsaall versions2.0.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.starkbank:ecdsa-java. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update com.starkbank:ecdsa-java to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9wx7-jrvc-28mm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-9wx7-jrvc-28mm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9wx7-jrvc-28mm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-9wx7-jrvc-28mm in your dependencies?

O3 detects GHSA-9wx7-jrvc-28mm across Maven, npm, NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.