Vulnerability in node-lmdb (CVE-2022-21164)
Summary
Vulnerability in node-lmdb (CVE-2022-21164). Risk of unauthorized operations or information disclosure. Exploitable via ToString. Mitigation: upgrade to 0.9.7 or later.
Original description
The description as published by the source.
The package node-lmdb before 0.9.7 is vulnerable to Denial of Service (DoS) when defining a non-invokable ToString value, which will cause a crash during type check.
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-2022-21164 has been found in node-lmdb.
Attackers can target a specific entry point like ToString over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade node-lmdb to 0.9.7 or later.
If unsure, ask your IT team or search "node-lmdb CVE-2022-21164" on the vendor's site.
CVE-2022-21164 (node-lmdb) — CWE-241
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ToString
Patched: 0.9.7 — 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.
A vulnerability (CWE-241) exists in node-lmdb. Attackers reach the vulnerable code path via ToString without authentication.
Check the vendor advisory for the affected versions of node-lmdb. Attack surface: ToString.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.9.7.
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-lmdb' . 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-lmdb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
node-lmdbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade node-lmdb to 0.9.7ステージング環境で 0.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web snyk.io