| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution. |
| The package asciitable.js before 1.0.3 are vulnerable to Prototype Pollution via the main function. |
| This affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution. |
| The package grpc before 1.24.4; the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition. |
| This affects all versions of package json-ptr. The issue occurs in the set operation (https://flitbit.github.io/json-ptr/classes/_src_pointer_.jsonpointer.htmlset) when the force flag is set to true. The function recursively set the property in the target object, however it does not properly check the key being set, leading to a prototype pollution. |
| All versions of package trim are vulnerable to Regular Expression Denial of Service (ReDoS) via trim(). |
| pathval before version 1.1.1 is vulnerable to prototype pollution. |
| This affects the package @tsed/core before 5.65.7. This vulnerability relates to the deepExtend function which is used as part of the utils directory. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program. |
| This affects the package chart.js before 2.9.4. The options parameter is not properly sanitized when it is processed. When the options are processed, the existing options (or the defaults options) are deeply merged with provided options. However, during this operation, the keys of the object being set are not checked, leading to a prototype pollution. |
| The package mathjs before 7.5.1 are vulnerable to Prototype Pollution via the deepExtend function that runs upon configuration updates. |
| All versions of package safetydance are vulnerable to Prototype Pollution via the set function. |
| The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function. |
| The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML. |
| All versions of package gedi are vulnerable to Prototype Pollution via the set function. |
| All versions of package safe-object2 are vulnerable to Prototype Pollution via the setter function. |
| All versions of package worksmith are vulnerable to Prototype Pollution via the setValue function. |
| All versions of package tiny-conf are vulnerable to Prototype Pollution via the set function. |
| All versions of package promisehelpers are vulnerable to Prototype Pollution via the insert function. |
| All versions of package nodee-utils are vulnerable to Prototype Pollution via the deepSet function. |
| All versions of package node-oojs are vulnerable to Prototype Pollution via the setPath function. |
