# CVE-2020-7678: Arbitrary Code Execution

> Attackers can execute arbitrary code via unsanitized parameters passed to the eval function in the node-import library.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L/E:P/RL:U/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pc62-cq5x-3j5g

## What is CVE-2020-7678?

CVE-2020-7678 is a high-severity code injection vulnerability in node-import, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects all versions of package node-import. The "params" argument of module function can be controlled by users without any sanitization.b. This is then provided to the “eval” function located in line 79 in the index file "index.js".

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

2 open source packages ship an affected version, including node-import. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-import` | npm | All versions to 0.9.2 | None |
| `node-import` | npm | All versions to 0.9.2 | None |

Products: Node-Import Project Node-Import.

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

No fix has been published for CVE-2020-7678 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7678 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7678 is a high-severity code injection vulnerability in node-import, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7678 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-import (npm): affected all versions up to 0.9.2; no fix listed
- node-import (npm): affected all versions up to 0.9.2; no fix listed

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

## Sources

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

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