Skip to content

Prototype pollution in dojo

High severity GitHub Reviewed Published Mar 10, 2020 in dojo/dojo • Updated Jan 27, 2023

Package

npm dojo (npm)

Affected versions

< 1.11.10
>= 1.12.0, < 1.12.8
>= 1.13.0, < 1.13.7
>= 1.14.0, < 1.14.6
>= 1.15.0, < 1.15.3
>= 1.16.0, < 1.16.2

Patched versions

1.11.10
1.12.8
1.13.7
1.14.6
1.15.3
1.16.2

Description

In affected versions of dojo (NPM package), the deepCopy method is vulnerable to Prototype Pollution.

Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.
An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values.

This has been patched in versions 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2

References

@dylans dylans published to dojo/dojo Mar 10, 2020
Reviewed Mar 10, 2020
Published to the GitHub Advisory Database Mar 10, 2020
Published by the National Vulnerability Database Mar 10, 2020
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

EPSS score

0.236%
(62nd percentile)

Weaknesses

CVE ID

CVE-2020-5258

GHSA ID

GHSA-jxfh-8wgv-vfr2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.