Skip to content
Fencer Intel
high 7.7

CVE-2020-5258 json

Prototype pollution in dojo

published 6y ago modified last mo. also GHSA-jxfh-8wgv-vfr2 , EUVD-2020-0349

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
4.0%
EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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

Patch / fix

  • npm dojo 1.11.10, 1.12.8, 1.13.7, 1.14.6, 1.15.3, 1.16.2
  • linuxfoundation dojo 1.11.10, 1.12.8, 1.13.7, 1.14.6, 1.15.3, 1.16.2
  • dojo Debian 14, Debian 13, Debian 12 1.15.3+dfsg1-1

debian advisories DEBIAN-CVE-2020-5258

Is CVE-2020-5258 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-5258 updated cvss 3.7

dojo: Prototype pollution in deepCopy method could result in code injection

  • Red Hat Satellite 5 dojo
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

4.02% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/dojo/dojo/security/advisories/GHSA-jxfh-8wgv-vfr2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm dojo
<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
1.11.10
1.12.8
1.13.7
1.14.6
1.15.3
1.16.2

Affected products

  • dojo dojo

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-1321 Improperly Controlled Modification of Object Prototype Attributes
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.