# CVE-2020-5258: Prototype pollution in dojo > Prototype pollution in dojo's deepCopy method allows attackers to inject properties into object prototypes, potentially leading to code execution or privilege escalation. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Mar 2020 - **Updated:** 8 Oct 2026 - **Also known as:** DEBIAN-CVE-2020-5258, GHSA-jxfh-8wgv-vfr2, UBUNTU-CVE-2020-5258 ## What is CVE-2020-5258? CVE-2020-5258 is a high-severity code injection vulnerability in Debian Debian Linux, published on 10 Mar 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official 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 Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes), CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2020-5258? 12 open source packages ship an affected version, including dojo. It affects 10 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `dojo` | npm | All versions | 1.11.10 | | `dojo` | npm | All versions | 1.11.10 | | `dojo` | npm | From 1.12.0 | 1.12.8 | | `dojo` | npm | From 1.12.0 | 1.12.8 | | `dojo` | npm | From 1.13.0 | 1.13.7 | | `dojo` | npm | From 1.13.0 | 1.13.7 | | `dojo` | npm | From 1.14.0 | 1.14.6 | | `dojo` | npm | From 1.14.0 | 1.14.6 | | `dojo` | npm | From 1.15.0 | 1.15.3 | | `dojo` | npm | From 1.15.0 | 1.15.3 | | `dojo` | npm | From 1.16.0 | 1.16.2 | | `dojo` | npm | From 1.16.0 | 1.16.2 | Products: Debian Debian Linux, Linuxfoundation Dojo, Oracle Communications Application Session Controller, Oracle Communications Policy Management, Oracle Communications Pricing Design Center, Oracle Documaker, Oracle Mysql, Oracle Primavera Unifier, Oracle Webcenter Sites, Oracle Weblogic Server. ## How do I fix CVE-2020-5258? Upgrade dojo to a fixed version for your release line: 1.11.10, 1.12.8, 1.13.7 or 1.14.6. ## Is CVE-2020-5258 being exploited? There is no known exploitation of CVE-2020-5258 in the wild and no public exploit code. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-5258 and fix it if it is affected. What it is: CVE-2020-5258 is a high-severity code injection vulnerability in Debian Debian Linux, published on 10 Mar 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2020-5258 in the wild and no public exploit code. Affected packages and fixed versions: - dojo (npm): affected all versions; fixed in 1.11.10 - dojo (npm): affected all versions; fixed in 1.11.10 - dojo (npm): affected from 1.12.0; fixed in 1.12.8 - dojo (npm): affected from 1.12.0; fixed in 1.12.8 - dojo (npm): affected from 1.13.0; fixed in 1.13.7 - dojo (npm): affected from 1.13.0; fixed in 1.13.7 - dojo (npm): affected from 1.14.0; fixed in 1.14.6 - dojo (npm): affected from 1.14.0; fixed in 1.14.6 - dojo (npm): affected from 1.15.0; fixed in 1.15.3 - dojo (npm): affected from 1.15.0; fixed in 1.15.3 - dojo (npm): affected from 1.16.0; fixed in 1.16.2 - dojo (npm): affected from 1.16.0; fixed in 1.16.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-5258/ (Markdown: https://insights.sbomify.com/CVE-2020-5258/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5258 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5258 - OSV: https://osv.dev/vulnerability/CVE-2020-5258 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-5258/ Summaries are generated and may contain mistakes; the official description above is the record.