CVE-2021-43571: Improper Verification of Cryptographic Signature in starkbank-ecdsa

starkbank-ecdsa Updated 02 Oct 2025

Summary

10/11/2021
Yes i
Critical
9.8

CVE-2021-43571: Improper Verification of Cryptographic Signature in starkbank-ecdsa. Affects starkbank-ecdsa versions < 1.1.3. Fixed in 1.1.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The starkbank-ecdsa package is an npm package used for ECDSA (Elliptic Curve Digital Signature Algorithm) operations in Node.js applications. It provides functions for generating and verifying cryptographic signatures. The package is widely used in various applications that require secure digital signatures. However, a vulnerability has been discovered in version 1.1.2 of the package, which allows attackers to forge signatures on arbitrary messages.

Vulnerability Detail

The vulnerability in starkbank-ecdsa version 1.1.2 lies in the verify function of the ECDSA library. The function fails to properly check that the signature is non-zero, which means that an attacker can create a valid signature for any message without possessing the private key. This allows them to impersonate legitimate users or tamper with signed data. The impact of this vulnerability is critical as it undermines the integrity and authenticity of digital signatures, compromising the security of applications relying on this package.

How To Fix

Latest published version: 1.2.0 as of 22 Oct 2026

npm install starkbank-ecdsa@1.2.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.3

This is the first release that contains the fix.

npm install starkbank-ecdsa@1.1.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of the starkbank-ecdsa package to address the issue.

Conclusion

The vulnerability in starkbank-ecdsa version 1.1.2 allows attackers to forge signatures on arbitrary messages, compromising the integrity and authenticity of digital signatures. It is crucial for developers to upgrade to version 1.1.3 or later of the package to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for starkbank-ecdsa →

Share this vulnerability

FAQ

starkbank-ecdsa is an npm package used for ECDSA operations in Node.js applications. It provides functions for generating and verifying cryptographic signatures.

The vulnerability allows attackers to forge signatures on arbitrary messages, compromising the integrity and authenticity of digital signatures.

To fix this vulnerability, upgrade to version 1.1.3 or later of the starkbank-ecdsa package.

No, there are no known workarounds for this vulnerability. Upgrading to the fixed version is the recommended solution.

You can find more information about this vulnerability in the GitHub Advisory Database and the provided source link.

Related vulnerabilities

Recent vulnerabilities recorded for starkbank-ecdsa.

How To Fix

Latest published version: 1.2.0 as of 22 Oct 2026

npm install starkbank-ecdsa@1.2.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.1.3

This is the first release that contains the fix.

npm install starkbank-ecdsa@1.1.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback