Yuhan Gao

The package contains a Prototype Pollution issue in the ` merge()` function within the `merge.js` file. This allows modification of the `constructor.prototype`, potentially leading to code execution if errors are caught and user-supplied search parameters are injected. This is a distinct issue from another reported problem. The vulnerability is not exploitable in the default configuration of InstantSearch because search parameters are not user-modifiable.

The issue arises from improper input sanitization in the `setProperty()` function, allowing the usage of arguments like ` proto ` and leading to Prototype Pollution. This can be exploited due to the lack of proper input validation.

The issue concerns Prototype Pollution via the `nest()` function in the `flatnest/nest.js` file. This affects all versions of the package flatnest.

The issue concerns Prototype Pollution via the `extend()` function in the `utils.js` file. This affects the progressbar.js package.

The issue is related to Prototype Pollution due to insufficient checks. It can be exploited via the `set()` function and the `current` variable in the `/dottie.js` file.

The issue concerns Prototype Pollution via the `extend` function in `Collection.js/dist/node/iterators/extend.js`. This affects versions of the package collection.js before 6.8.1.

The issue concerns Prototype Pollution via the `set()` function in the `index.js` file. This affects all versions of the dot-lens package. There is no information provided about the estimated number of potentially affected devices worldwide or details about real-world incidents where this issue was exploited.

The issue concerns Prototype Pollution via the ` mix` function. This affects all versions of the package utilities. There is no information provided about the estimated number of potentially affected devices worldwide or details about real-world incidents where this issue was exploited.

The issue concerns Prototype Pollution in the rangy package. It occurs when using the `extend()` function in the file `rangy-core.js`, which utilizes a recursive merge. This can allow an attacker to modify properties of the `Object.prototype`.

The issue allows an attacker to add or modify properties of the Object.prototype through Prototype Pollution when using the function safeEval. This is due to the function's use of the vm variable, enabling an attacker to modify properties of the Object.prototype.

The issue allows alteration of all Object attributes, including magical attributes such as `proto`, `constructor`, and `prototype`, leading to Prototype Pollution.