Skip to content
This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2020-28498 →
Unrated

Vulnerability in node-elliptic

DEBIAN-CVE-2020-28498 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2020-28498 has been found in node-elliptic.
Confidential information can be exposed externally.
What to do: upgrade node-elliptic to 6.5.4~dfsg-1 or later.
If unsure, ask your IT team or search "node-elliptic DEBIAN-CVE-2020-28498" on the vendor's site.

DEBIAN-CVE-2020-28498 (node-elliptic)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.5.4~dfsg-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in node-elliptic.

Affected scope

Check the vendor advisory for the affected versions of node-elliptic.

Severity

Severity: ?. Confidential information can be exposed externally.

How to fix

Update to 6.5.4~dfsg-1.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node-elliptic' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    grep -r 'node-elliptic' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で node-elliptic を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade node-elliptic to 6.5.4~dfsg-1

    ステージング環境で 6.5.4~dfsg-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Debian:12 node-elliptic
< 6.5.4~dfsg-1
6.5.4~dfsg-1
Debian:13 node-elliptic
< 6.5.4~dfsg-1
6.5.4~dfsg-1
Debian:14 node-elliptic
< 6.5.4~dfsg-1
6.5.4~dfsg-1
Original description The description as published by the source.

The package elliptic before 6.5.4 are vulnerable to Cryptographic Issues via the secp256k1 implementation in elliptic/ec/key.js. There is no check to confirm that the public key point passed into the derive function actually exists on the secp256k1 curve. This results in the potential for the private key used in this implementation to be revealed after a number of ECDH operations are performed.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details