How severe is GHSA-9wx7-jrvc-28mm?

No CVSS score has been assigned to GHSA-9wx7-jrvc-28mm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9wx7-jrvc-28mm?

GHSA-9wx7-jrvc-28mm affects the following packages: com.starkbank:ecdsa-java (Maven), starkbank-ecdsa (npm), starkbank-ecdsa (NuGet), starkbank-ecdsa (PyPI). Ecosystems affected: Maven, npm, NuGet, PyPI.

How do I fix GHSA-9wx7-jrvc-28mm?

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.

How do I detect GHSA-9wx7-jrvc-28mm in my Maven, npm, NuGet, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.starkbank:ecdsa-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9wx7-jrvc-28mm if there is no patch (or I can't update yet)?

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.

Is GHSA-9wx7-jrvc-28mm actively exploited in the wild?

No public exploit code has been indexed for GHSA-9wx7-jrvc-28mm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9wx7-jrvc-28mm published, and has it been updated?

GHSA-9wx7-jrvc-28mm was published on November 8, 2021 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Signature verification vulnerability in Stark Bank ecdsa…

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

29other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

starkbank-ecdsanpm

547Kdownloads / week

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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.starkbank:ecdsa-java`	≥ 1.0.0&&< 1.0.1	1.0.1`com.starkbank:ecdsa-java:1.0.1`
📦npm	`starkbank-ecdsa`	≥ 1.1.2&&< 1.1.3	1.1.3`npm install starkbank-ecdsa@1.1.3`
.NETNuGet	`starkbank-ecdsa`	≥ 1.3.1&&< 1.3.2	1.3.2`dotnet add package starkbank-ecdsa --version 1.3.2`
🐍PyPI	`starkbank-ecdsa`	all versions	2.0.1`pip install --upgrade 'starkbank-ecdsa==2.0.1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.starkbank:ecdsa-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
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.

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?

Find it across Maven, npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works

Signature verification vulnerability in Stark Bank ecdsa librariesGHSA-9wx7-jrvc-28mm