Information Disclosure in node-etsy-client (CVE-2021-21421)
Summary
Vulnerability in node-etsy-client (CVE-2021-21421). Confidential information can be exposed externally. Mitigation: upgrade to 0.3.0 or later.
Original description
The description as published by the source.
Impact
What kind of vulnerability is it? Who is impacted?
Applications that are using node-etsy-client and reporting client error to the end user will offer api key value too
Patches
Has the problem been patched? What versions should users upgrade to?
creharmony/node-etsy-client#18 fixes this issue. This is fixed in node-etsy-client v0.3.0 and later.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not report or log etsy client error if you are using version <= v0.2.0
Update your version of node-etsy-client
References
Are there any links users can visit to find out more?
- https://github.com/creharmony/node-etsy-client/issues/17 : On connect error secret appears in error #17
For more information
If you have any questions or comments about this advisory:
- Open an issue in github.com/creharmony/node-etsy-client/issues
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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 CVE-2021-21421 has been found in node-etsy-client.
Confidential information can be exposed externally.
What to do: upgrade node-etsy-client to 0.3.0 or later.
If unsure, ask your IT team or search "node-etsy-client CVE-2021-21421" on the vendor's site.
CVE-2021-21421 (node-etsy-client) — CWE-200
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.3.0 — 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.
Information disclosure (CWE-200) exists in node-etsy-client.
Check the vendor advisory for the affected versions of node-etsy-client.
Severity: ?. Confidential information can be exposed externally.
Update to 0.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node-etsy-client' . 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
-
1Identify exposure identify
grep -r 'node-etsy-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
node-etsy-clientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade node-etsy-client to 0.3.0ステージング環境で 0.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com