CVE-2021-23558: Prototype Pollution in bmoor

bmoor Updated 02 Oct 2025

Summary

01/02/2022
Yes i
High
7.3

CVE-2021-23558: Prototype Pollution in bmoor. Affects bmoor versions < 0.10.1. Fixed in 0.10.1. 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 bmoor package is an npm package that provides various utility functions for JavaScript applications. It is widely used in many projects and offers features such as data manipulation, validation, and more. However, versions prior to 0.10.1 are vulnerable to Prototype Pollution due to missing sanitization in the set function.

Vulnerability Detail

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior in the application. In the case of bmoor, the set function does not properly sanitize user input, allowing an attacker to inject malicious properties into the prototype chain. This can lead to various security issues, including remote code execution, data manipulation, and privilege escalation.

How To Fix

Minimum fixed version

0.10.1

This is the first release that contains the fix.

npm install bmoor@0.10.1

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

Workaround

If upgrading to the latest version is not immediately feasible, developers can mitigate the risk by implementing input validation and sanitization in their application code. This involves carefully validating and filtering user input before passing it to the vulnerable functions in bmoor. By ensuring that only safe and expected values are processed, the risk of Prototype Pollution can be significantly reduced.

Conclusion

The bmoor package prior to version 0.10.1 is vulnerable to Prototype Pollution, which can lead to serious security issues. It is crucial for developers to upgrade to the latest version or apply input validation and sanitization to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for bmoor →

Share this vulnerability

FAQ

Prototype Pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior in the application. It can be exploited to execute arbitrary code, manipulate data, or escalate privileges.

The bmoor package becomes vulnerable to Prototype Pollution due to missing sanitization in the set function. This allows an attacker to inject malicious properties into the prototype chain of objects.

The potential consequences of this vulnerability include remote code execution, data manipulation, and privilege escalation. An attacker can exploit the Prototype Pollution issue in bmoor to execute arbitrary code or modify critical data within the application.

Yes, a fix is available for this vulnerability in version 0.10.1 of the bmoor package. It is recommended to upgrade to this version or later to mitigate the risk of Prototype Pollution.

If upgrading to the latest version is not immediately feasible, developers can implement input validation and sanitization in their application code to mitigate the risk. By carefully validating and filtering user input, the chances of an attacker exploiting the Prototype Pollution issue can be reduced.

Related vulnerabilities

Recent vulnerabilities recorded for bmoor.

How To Fix

Minimum fixed version

0.10.1

This is the first release that contains the fix.

npm install bmoor@0.10.1

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