# CVE-2020-7709: Prototype Pollution

> Prototype pollution in json-pointer allows attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7mg4-w3w5-x5pc

## What is CVE-2020-7709?

CVE-2020-7709 is a medium-severity vulnerability in json-pointer, published on 5 Oct 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

This affects the package json-pointer before 0.6.1. Multiple reference of object using slash is supported.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

4 open source packages ship an affected version, including org.webjars.npm:json-pointer and json-pointer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.webjars.npm:json-pointer` | Maven | All versions | 0.6.1 |
| `org.webjars.npm:json-pointer` | Maven | All versions | 0.6.1 |
| `json-pointer` | npm | All versions | 0.6.1 |
| `json-pointer` | npm | All versions | 0.6.1 |

Products: Manuelstofer Json-Pointer.

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

Upgrade org.webjars.npm:json-pointer to 0.6.1 or later.

## Is CVE-2020-7709 being exploited?

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

## Other vulnerabilities in json-pointer

- [CVE-2021-23820](https://insights.sbomify.com/CVE-2021-23820/): Prototype Pollution (medium 5.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7709 is a medium-severity vulnerability in json-pointer, published on 5 Oct 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7709 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.webjars.npm:json-pointer (Maven): affected all versions; fixed in 0.6.1
- org.webjars.npm:json-pointer (Maven): affected all versions; fixed in 0.6.1
- json-pointer (npm): affected all versions; fixed in 0.6.1
- json-pointer (npm): affected all versions; fixed in 0.6.1

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-7709/ (Markdown: https://insights.sbomify.com/CVE-2020-7709/index.md)
```

## Sources

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

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