Weakness (CWE)
CWE-1321: Improperly Controlled Modification of Object Prototype Attributes
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
How to prevent it (5 mitigations)
-
Implementation
By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
-
Architecture and Design
By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
-
Implementation
When handling untrusted objects, validating using a schema can be used.
-
Implementation
By using an object without prototypes (via Object.create(null) ), adding object prototype attributes by accessing the prototype via the special attributes becomes impossible, mitigating this weakness.
-
Implementation
Map can be used instead of objects in most cases. If Map methods are used instead of object attributes, it is not possible to access the object prototype or modify it.
Source: MITRE CWE-1321
712 results · Feed
-
High —
Prototype Pollution in handlebars
Versions of `handlebars` prior to 3.0.8 or 4.5.3 are vulnerable to prototype pollution. It is possible to add or modify properties to the Object prototype through a malicious template. This may allow attackers to crash the application or execute Arbitrary Cod…
-
High —
Prototype Pollution in mithril
Affected versions of `mithril`are vulnerable to prototype pollution. The function `parseQueryString` may allow a malicious user to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects. A…
-
High —
Prototype Pollution in lodash.mergewith
Versions of `lodash.mergewith` before 4.6.2 are vulnerable to prototype pollution. The function `mergeWith` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an exist…
-
High —
Prototype Pollution in lodash.defaultsdeep
Versions of `lodash.defaultsdeep` before 4.6.1 are vulnerable to Prototype Pollution. The function 'defaultsDeep' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that …
-
High —
Prototype Pollution in lodash.mergewith
Versions of `lodash.mergewith` before 4.6.1 are vulnerable to Prototype Pollution. The function 'mergeWith' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will e…
-
High —
Prototype Pollution in lodash.defaultsdeep
Versions of `lodash.defaultsdeep` before 4.6.1 are vulnerable to prototype pollution. The function `mergeWith` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an ex…
-
High —
Prototype Pollution in lodash.merge
Versions of `lodash.merge` before 4.6.1 are vulnerable to Prototype Pollution. The function 'merge' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on …
-
High —
Prototype Pollution in lodash.merge
Versions of `lodash.merge` before 4.6.2 are vulnerable to prototype pollution. The function `merge` may allow a malicious user to modify the prototype of `Object` via `{constructor: {prototype: {...}}}` causing the addition or modification of an existing prop…
-
High —
Prototype Pollution in @commercial/subtext
Versions of `@commercial/subtext` prior to 5.1.2 are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may…
-
High —
Prototype Pollution in @hapi/subtext
Versions of `@hapi/pez` prior to 4.1.2 or 5.0.1 are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may …
-
High —
Prototype Pollution in pez
All versions of `pez` are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation ru…
-
Medium —
Prototype Pollution in smart-extend
All versions of `smart-extend` are vulnerable to Prototype Pollution. The `deep()` function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects. ## Recommendation No fi…
-
Low —
Prototype Pollution in merge-objects
All versions of `merge-objects` are vulnerable to Prototype Pollution. ## Recommendation No fix is available for this vulnerability at this time. It is our recommendation to use an alternative package.
-
Critical 9.8
Prototype Pollution
All versions of package worksmith are vulnerable to Prototype Pollution via the setValue function.
-
Critical 9.8
Prototype Pollution
All versions of package safe-object2 are vulnerable to Prototype Pollution via the setter function.
-
Critical 9.8
Prototype Pollution
All versions of package gedi are vulnerable to Prototype Pollution via the set function.
-
Critical 9.8
Prototype Pollution
All versions of package promisehelpers are vulnerable to Prototype Pollution via the insert function.
-
Critical 9.8
Prototype Pollution
All versions of package tiny-conf are vulnerable to Prototype Pollution via the set function.
-
Critical 9.8
Prototype Pollution
All versions of package node-oojs are vulnerable to Prototype Pollution via the setPath function.
-
Critical 9.8
Prototype Pollution
All versions of package nodee-utils are vulnerable to Prototype Pollution via the deepSet function.
-
Critical 9.8
Prototype Pollution
The package node-forge before 0.10.0 is vulnerable to Prototype Pollution via the util.setPath function. Note: Version 0.10.0 is a breaking change removing the vulnerable functions.
-
Critical 9.8
Prototype Pollution
Versions of package locutus before 2.0.12 are vulnerable to prototype Pollution via the php.strings.parse_str function.
-
Critical 9.8
Prototype Pollution
All versions of package dot-notes are vulnerable to Prototype Pollution via the create function.
-
Critical 9.8
Prototype Pollution
All versions of package gammautils are vulnerable to Prototype Pollution via the deepSet and deepMerge functions.
-
Critical 9.8
Prototype Pollution
All versions of package confucious are vulnerable to Prototype Pollution via the set function.
-
Critical 9.8
Prototype Pollution
All versions of package deep-get-set are vulnerable to Prototype Pollution via the main function.
-
Critical 9.8
Prototype Pollution
All versions of package deeps are vulnerable to Prototype Pollution via the set function.
-
Critical 9.8
Prototype Pollution
All versions of package arr-flatten-unflatten are vulnerable to Prototype Pollution via the constructor.
-
Critical 9.8
Prototype Pollution
The package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions.
-
Critical 9.8
Prototype Pollution
The package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.
-
Critical 9.8
Prototype Pollution
The package connie-lang before 0.1.1 are vulnerable to Prototype Pollution in the configuration language library used by connie.
-
Critical 9.8
Prototype Pollution
The package linux-cmdline before 1.0.1 are vulnerable to Prototype Pollution via the constructor.
-
Critical 9.8
Prototype Pollution
All versions of package nis-utils are vulnerable to Prototype Pollution via the setValue function.
-
Critical 9.8
Prototype Pollution
All versions of package templ8 are vulnerable to Prototype Pollution via the parse function.
-
Critical 9.8
Prototype Pollution
madlib-object-utils before 0.1.7 is vulnerable to Prototype Pollution via setValue.
-
Critical 9.8
Prototype Pollution
All versions of phpjs are vulnerable to Prototype Pollution via parse_str.
-
High 7.5CVE-2020-7699 Public exploit
Prototype Pollution
This affects the package express-fileupload before 1.1.8. If the parseNested option is enabled, sending a corrupt HTTP request can lead to denial of service or arbitrary code execution.
-
Medium 5.6
Prototype Pollution in Ajv
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the wo…
-
High 7.4CVE-2020-8203 Public exploit
Prototype Pollution in lodash
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
-
High 7.3
Prototype Pollution
In all versions of package casperjs, the mergeObjects utility function is susceptible to Prototype Pollution.