CVE-2022-21164: Unhandled case in node-lmdb leads to Denial of Service

node-lmdb Updated 02 Oct 2025

Summary

17/03/2022
Yes i
High
7.5

CVE-2022-21164: Unhandled case in node-lmdb. Affects node-lmdb versions < 0.9.7. Fixed in 0.9.7. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The node-lmdb package is an npm package that provides a Node.js binding for the Lightning Memory-Mapped Database (LMDB) library. LMDB is a highly efficient, transactional key-value store that allows multiple processes to access the same database concurrently. The node-lmdb package enables developers to use LMDB in their Node.js applications, providing a simple and efficient interface for database operations. However, versions of node-lmdb before 0.9.7 are vulnerable to a Denial of Service (DoS) attack.

Vulnerability Detail

The vulnerability in node-lmdb arises from an unhandled case when defining a non-invokable ToString value. This can lead to a crash during type check operations, resulting in a DoS condition. An attacker can exploit this vulnerability by providing a specially crafted input that triggers the unhandled case, causing the application to crash. The impact of this vulnerability is a disruption of service, potentially leading to downtime and loss of data.

How To Fix

Latest published version: 0.10.1 as of 23 Oct 2026

npm install node-lmdb@0.10.1

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

If you need the minimum change

0.9.7

This is the first release that contains the fix.

npm install node-lmdb@0.9.7

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 recommended to update to the fixed version of the node-lmdb package as soon as possible.

Conclusion

The node-lmdb package before version 0.9.7 is vulnerable to a Denial of Service (DoS) attack due to an unhandled case when defining a non-invokable ToString value. To mitigate this vulnerability, it is crucial to update the package to version 0.9.7 or later. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for node-lmdb →

Share this vulnerability

FAQ

Node-lmdb is an npm package that provides a Node.js binding for the Lightning Memory-Mapped Database (LMDB) library. It allows developers to use LMDB in their Node.js applications for efficient and concurrent database operations.

The vulnerability in node-lmdb can lead to a Denial of Service (DoS) condition, causing the application to crash. This can result in downtime and potential loss of data.

To fix this vulnerability, update your node-lmdb package to version 0.9.7 or later. Run the command 'npm install node-lmdb@0.9.7' in your project directory.

There is no known workaround for this vulnerability. It is recommended to update to the fixed version of the node-lmdb package.

You can find more information about node-lmdb on the npm package page or the official GitHub repository.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Latest published version: 0.10.1 as of 23 Oct 2026

npm install node-lmdb@0.10.1

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

If you need the minimum change

0.9.7

This is the first release that contains the fix.

npm install node-lmdb@0.9.7

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