# CVE-2020-5259: Prototype Pollution in Dojox

> An attacker can exploit prototype pollution in the Dojox jqMix method to inject properties and potentially execute arbitrary code.

- **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:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-5259, GHSA-3hw5-q855-g6cw, UBUNTU-CVE-2020-5259

## What is CVE-2020-5259?

CVE-2020-5259 is a high-severity code injection vulnerability in dojox, 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 dojox (NPM package), the jqMix 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.11.10, 1.12.8, 1.13.7, 1.14.6, 1.15.3 and 1.16.2

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2020-5259?

12 open source packages ship an affected version, including dojox. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dojox` | npm | All versions | 1.11.10 |
| `dojox` | npm | All versions | 1.11.10 |
| `dojox` | npm | From 1.12.0 | 1.12.8 |
| `dojox` | npm | From 1.12.0 | 1.12.8 |
| `dojox` | npm | From 1.13.0 | 1.13.7 |
| `dojox` | npm | From 1.13.0 | 1.13.7 |
| `dojox` | npm | From 1.14.0 | 1.14.6 |
| `dojox` | npm | From 1.14.0 | 1.14.6 |
| `dojox` | npm | From 1.15.0 | 1.15.3 |
| `dojox` | npm | From 1.15.0 | 1.15.3 |
| `dojox` | npm | From 1.16.0 | 1.16.2 |
| `dojox` | npm | From 1.16.0 | 1.16.2 |

Products: Linuxfoundation Dojox.

## How do I fix CVE-2020-5259?

Upgrade dojox to a fixed version for your release line: 1.11.10, 1.12.8, 1.13.7 or 1.14.6.

## Is CVE-2020-5259 being exploited?

There is no known exploitation of CVE-2020-5259 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5259 and fix it if it is affected.

What it is: CVE-2020-5259 is a high-severity code injection vulnerability in dojox, 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-5259 in the wild and no public exploit code.

Affected packages and fixed versions:
- dojox (npm): affected all versions; fixed in 1.11.10
- dojox (npm): affected all versions; fixed in 1.11.10
- dojox (npm): affected from 1.12.0; fixed in 1.12.8
- dojox (npm): affected from 1.12.0; fixed in 1.12.8
- dojox (npm): affected from 1.13.0; fixed in 1.13.7
- dojox (npm): affected from 1.13.0; fixed in 1.13.7
- dojox (npm): affected from 1.14.0; fixed in 1.14.6
- dojox (npm): affected from 1.14.0; fixed in 1.14.6
- dojox (npm): affected from 1.15.0; fixed in 1.15.3
- dojox (npm): affected from 1.15.0; fixed in 1.15.3
- dojox (npm): affected from 1.16.0; fixed in 1.16.2
- dojox (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-5259/ (Markdown: https://insights.sbomify.com/CVE-2020-5259/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5259
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5259
- OSV: https://osv.dev/vulnerability/CVE-2020-5259

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-5259/
Summaries are generated and may contain mistakes; the official description above is the record.