This repository has been archived by the owner on Apr 24, 2024. It is now read-only.
Prototype Pollution in lodash vulnerable CVE-2020-8203 #1365
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the bugs: 馃悰
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.
Affected versions of this package are vulnerable to Prototype Pollution. The function
zipObjectDeep
can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as
__proto__
,constructor
andprototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on theObject.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.PoC
There are two main ways in which the pollution of prototypes occurs:
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
When the source object contains a property named
__proto__
defined withObject.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype ofObject
and the source ofObject
as defined by the attacker. Properties are then copied on theObject
prototype.Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object:
merge({},source)
.lodash
andHoek
are examples of libraries susceptible to recursive merge attacks.Affected environments
CVE-2020-8203
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
GHSA-p6mc-m468-83gw