# CVE-2022-36010: Arbitrary code execution via function parsing in react-editable-json-tree

> Attackers can execute arbitrary code via eval in react-editable-json-tree when displaying untrusted JSON data.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-j3rv-w43q-f9x2

## What is CVE-2022-36010?

CVE-2022-36010 is a critical code injection vulnerability in oxyno-zeta react-editable-json-tree, published on 15 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This library allows strings to be parsed as functions and stored as a specialized component, [`JsonFunctionValue`](https://github.com/oxyno-zeta/react-editable-json-tree/blob/09a0ca97835b0834ad054563e2fddc6f22bc5d8c/src/components/JsonFunctionValue.js). To do this, Javascript's [`eval`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval) function is used to execute strings that begin with "function" as Javascript. This unfortunately could allow arbitrary code to be executed if it exists as a value within the JSON structure being displayed. Given that this component may often be used to display data from arbitrary, untrusted sources, this is extremely dangerous. One important note is that users who have defined a custom [`onSubmitValueParser`](https://github.com/oxyno-zeta/react-editable-json-tree/tree/09a0ca97835b0834ad054563e2fddc6f22bc5d8c#onsubmitvalueparser) callback prop on the [`JsonTree`](https://github.com/oxyno-zeta/react-editable-json-tree/blob/09a0ca97835b0834ad054563e2fddc6f22bc5d8c/src/JsonTree.js) component should be ***unaffected***. This vulnerability exists in the default `onSubmitValueParser` prop which calls [`parse`](https://github.com/oxyno-zeta/react-editable-json-tree/blob/master/src/utils/parse.js#L30). Prop is added to `JsonTree` called `allowFunctionEvaluation`. This prop will be set to `true` in v2.2.2, which allows upgrade without losing backwards-compatibility. In v2.2.2, we switched from using `eval` to using [`Function`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function) to construct anonymous functions. This is better than `eval` for the following reasons: - Arbitrary code should not be able to execute immediately, since the `Function` constructor explicitly *only creates* anonymous functions - Functions are created without local closures, so they only have access to the global scope If you use: - **Version `<2.2.2`**, you must upgrade as soon as possible. - **Version `^2.2.2`**, you must explicitly set `JsonTree`'s `allowFunctionEvaluation` prop to `false` to fully mitigate this vulnerability. - **Version `>=3.0.0`**, `allowFunctionEvaluation` is already set to `false` by default, so no further steps are necessary.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2022-36010?

2 open source packages ship an affected version, including react-editable-json-tree. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-editable-json-tree` | npm | All versions | 2.2.2 |
| `react-editable-json-tree` | npm | All versions | 2.2.2 |

Products: React Editable Json Tree Project React Editable Json Tree.

## How do I fix CVE-2022-36010?

Upgrade react-editable-json-tree to 2.2.2 or later.

## Is CVE-2022-36010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36010 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36010 and fix it if it is affected.

What it is: CVE-2022-36010 is a critical code injection vulnerability in oxyno-zeta react-editable-json-tree, published on 15 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36010 exists.

Affected packages and fixed versions:
- react-editable-json-tree (npm): affected all versions; fixed in 2.2.2
- react-editable-json-tree (npm): affected all versions; fixed in 2.2.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-2022-36010/ (Markdown: https://insights.sbomify.com/CVE-2022-36010/index.md)
```

## Sources

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

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